home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!noc.near.net!hri.com!spool.mu.edu!wupost!darwin.sura.net!haven.umd.edu!mimsy!alex
- From: alex@cs.umd.edu (Alex Blakemore)
- Newsgroups: comp.sys.next.programmer
- Subject: Re: setting a button key to be ESC
- Message-ID: <60141@mimsy.umd.edu>
- Date: 7 Sep 92 21:25:28 GMT
- References: <Bu68tK.37L@cs.psu.edu> <1992Sep7.150548.8473@next.cambridge.ma.us> <SCOTT.92Sep7160540@nic.gac.edu>
- Sender: news@mimsy.umd.edu
- Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
- Lines: 24
-
- In article <SCOTT.92Sep7160540@nic.gac.edu> scott@nic.gac.edu (Scott Hess) writes:
- > What gave it away to me is when I ran IB, pulled in a Panel, but
- > a Button on it, made the Key for it a 'd', and then did a Run/Test.
- > Pressing d caused the Button to flash, regardless of whether I had
- > Command down or not. [Really, try it, it works.]
-
- its even documented in (2.X)
- /NextLibrary/Documentation/NextDev/NextStep/Reference/02_Classes/AppKit/Panel.rtf
-
- - keyDown:(NXEvent *)theEvent
-
- Translates the key-down event into a commandKey: message for the
- Panel, thus interpreting the event as a potential keyboard
- alternative. If the Panel has a button that displays the Return
- symbol and the key-down event is for the Return key, it will operate
- the button.
-
- A Panel can receive keyDown: event messages only when it's the key
- window and none of its Views is the first responder.
-
-
- --
- ---------------------------------------------------
- Alex Blakemore alex@cs.umd.edu NeXT mail accepted
-