Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!ames!dftsrv!kong!vesper From: vesper@kong.gsfc.nasa.gov (Greg Vesper - RMS) Newsgroups: comp.sys.next Subject: Re: NOT (click to type) in NeXTStep? Message-ID: Date: 8 Nov 90 16:33:49 GMT References: <8516@darkstar.ucsc.edu> <25251@uflorida.cis.ufl.EDU> <10357@ubc-cs.UUCP> Sender: news@dftsrv.gsfc.nasa.gov Lines: 19 In <10357@ubc-cs.UUCP> morrison@cs.ubc.ca (Rick Morrison) writes: >I moved from an X-windows environment to NeXTStep about a year and a half ago. >I too initially despised click to type. By now, of course, I am quite used >to it, and actually appreciate its conservative behaviour from time to >time. The problem that I still have with the interface is the marriage of >click-in-window with bring-window-to-top-and-make-current. It should >be possible to make a window current without bringing it to top. I >am forever shifting windows around in order to view some small >fraction of the contents of each window concurrently. I couldn't agree more.. Everytime I activate a window, even if its just for a quick keystroke, my whole desktop gets rearranged - menus change, windows overlap - yuk. Its very inelegant I think. -- Greg Vesper (vesper@kong.gsfc.nasa.gov) 301-286-5162 Goddard Space Flight Center; Greenbelt, Maryland "Two basic facts of life: 1) There is a God. 2) You're not him."