Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!uflorida!gatech!rutgers!aramis.rutgers.edu!remus.rutgers.edu!declan From: declan@remus.rutgers.edu (Declan McCullagh/LZ) Newsgroups: comp.sys.next Subject: Re: NOT (click to type) in NeXTStep? Summary: Problem solved... Message-ID: Date: 6 Nov 90 21:20:07 GMT References: <8516@darkstar.ucsc.edu> <10357@ubc-cs.UUCP> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 22 In article <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'd like to allow one fact to enter this otherwise totally subjective discussion: NeXTstep v2.0 DOES allow you to view other windows by using Command-Up and Command-Down arrow. It does NOT make the other windows the key window, though - there was a WindowServer hack on the archive servers a few months ago that would allow you to bind keystrokes to applications and switch between them in that manner. -Declan -------------------------------------------------------------------- Declan McCullagh / NeXT Campus Consultant \ declan@remus.rutgers.edu --------------------------------------------------------------------