Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!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? Message-ID: Date: 7 Nov 90 17:31:36 GMT References: <1990Oct28.165341.6949@cs.cmu.edu> <1990Nov6.221820.17987@informix.com> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 29 In article <1990Nov6.221820.17987@informix.com>, cortesi@informix.com (David Cortesi) writes: > 1) No way to send a window to the back. If you completely cover a > window, the only way to get at it is to iconize everything in front > of it. Yes, I know about double-clicking the application's icon in > the dock... But do you know about Command-DownArrow? > 2) No way to use a window without bringing it to the front. I found > many good uses for the SunView ability to interact with a window that > was partly obscured by other windows. Command-UpArrow and Command-DownArrow work here, too. Or you can Alternate-Click in a window's title bar (that works under NeXTstep 1.0). > 3) Click-to-activate can cause scrolling: if you want only to activate > a window, and only its left edge is showing, you will also cause a > scroll action when you click on it. This is covered in the online documentation and is a conscious decision by NeXT. It's sometimes very nice to be able to click on a window's close box and having it disappear without activating that application. -------------------------------------------------------------------- Declan McCullagh / NeXT Campus Consultant \ declan@remus.rutgers.edu --------------------------------------------------------------------