Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ucselx!bionet!raven.alaska.edu!milton!news
From: dwatola@nextasy2 (David Watola)
Newsgroups: comp.sys.next
Subject: Re: Command-Arrow_Keys (was: Re: Key-equivalent for "cancel")
Message-ID: <1991Jun21.235814.11784@milton.u.washington.edu>
Date: 21 Jun 91 23:58:14 GMT
References: <fk=lzmq@rpi.edu>
Sender: news@milton.u.washington.edu (News)
Organization: University of Washington
Lines: 38

Garance A. Drosehn write (regarding my description of modifying
/usr/lib/NextStep/windowPackage.ps)

> 
> While the idea of intercepting the command-. key sequence seems like an  
> *extremely* silly thing to do, the above did remind me of something else I  
> wanted.  It'd be nice (perhaps) if command-right_arrow and command-left_arrow  
> cycled you thru the windows of the active application.  Basically I want what  
> option-right_arrow and option-left_arrow do in Stuart, but I want that for  
all  
> applications.
> 
> Would that be easy to do?  Anybody else think it would be worth doing?

i have been told by someone who has done this that you CAN do this.  you
can change windowPackage.ps to change the interface.  he recommends that you
back it up and have a terminal on the serial port to recover from crashes.  i  
suspect that rebooting in single-user mode (console mode) would allow you
to fix it though.

as for changing so the arrows only cycle through the windows of the
active application, i suspect this is easy as changing the line 

true 0 /getWindows winexec

in the /_handleCommand routine of windowPackage.ps to something like

true currentcontext /getWindows winexec

since the zero means "check all contexts."

hey, if anybody tries this, please let me know.  even if the results are  
catastrophic ;)


dave watola
dwatola@nextasy2.eecs.wsu.edu
dwatola@yoda.eecs.wsu.edu