Path: utzoo!attcan!uunet!samsung!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!uw-beaver!ubc-cs!morrison From: morrison@cs.ubc.ca (Rick Morrison) Newsgroups: comp.sys.next Subject: Re: NOT (click to type) in NeXTStep? Message-ID: <10357@ubc-cs.UUCP> Date: 6 Nov 90 19:34:59 GMT References: <8516@darkstar.ucsc.edu> <25251@uflorida.cis.ufl.EDU> Sender: news@cs.ubc.ca Organization: University of British Columbia, Vancouver, B.C., Canada Lines: 14 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. ------------------------------- Rick Morrison | {alberta,uw-beaver,uunet}!ubc-cs!morrison Dept. of Computer Science| morrison@cs.ubc.ca Univ. of British Columbia| morrison%ubc.csnet@csnet-relay.arpa Vancouver, B.C. V6T 1W5 | morrison@ubc.csnet (ubc-csgrads=137.82.8.20) (604) 228-5010