Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!ncar!boulder!gore!jacob
From: jacob@gore.com (Jacob Gore)
Newsgroups: comp.sys.next
Subject: Re: NOT (click to type) in NeXTStep?
Message-ID: <130116@gore.com>
Date: 7 Nov 90 03:59:31 GMT
References: <1990Oct28.165341.6949@cs.cmu.edu>
Reply-To: jacob@gore.com (Jacob Gore)
Organization: Gore Enterprises
Lines: 18

morrison@cs.ubc.ca (Rick Morrison) writes:
>The problem that I still have with the interface is the marriage of
>click-in-window with bring-window-to-top-and-make-current. 

/ comp.sys.next / purtill@morley.rutgers.edu (Mark Purtill) / Nov  6, 1990 /
> 	Do I read this right?  The window you're typing in MUST be in
> front?

No.

If you click on a window (or drag it), it will come up front and become the
key window (if it can).  Alt-clicking on a window (or alt-dragging it)
brings it to the front without making it the key window (and it can
obscure, partially or completely, the key window).

Jacob
--
Jacob Gore		Jacob@Gore.Com			boulder!gore!jacob