Path: utzoo!attcan!uunet!know!zaphod.mps.ohio-state.edu!usc!apple!agate!shelby!neon!bourget From: bourget@Neon.Stanford.EDU (Trevor G Bourget) Newsgroups: comp.sys.next Subject: Re: NOT (click to type) in NeXTStep? Message-ID: <1990Nov6.000903.604@Neon.Stanford.EDU> Date: 6 Nov 90 00:09:03 GMT References: <1990Oct28.165341.6949@cs.cmu.edu> <8516@darkstar.ucsc.edu> Organization: Computer Science Department, Stanford University Lines: 11 It's true that having scads of windows pop up and go away just because you drag the mouse across their main window would be quite costly and rather annoying. But I don't understand why this behavior is considered synonymous with a non-click-to-type interface. The only change needed to implement this functionality, in my opinion, would be that, whenever a key is pressed, a makeKeyWindow message would be sent to the window under the mouse; if it doesn't become the key window, the input would just go to the existing key window. Given the typing speed of most folks, I don't think this would be considered an unacceptable resource consumption in order to obtain the user interface they desire. -- Trevor (bourget@neon.stanford.edu)