FATQW@USU.BITNET (02/21/88)
(Hey CATS, are you writing these down? :-)
Ok, one more...
Make a new Intuition IDCMP class - HELPKEY. If it's enabled, and the user
presses the HELP key, it sends this class rather than RAWKEY. This way we
won't have to worry about RAWKEY just to see if the user pressed HELP.
Bryan
Bryan Ford //// A computer does what \\\\
Snail: 1790 East 1400 North //// you tell it to do, not \\\\
Logan, UT 84321 \\\XX/// what you want it to do. \\\XX///
Email: FATQW@USU.BITNET \XXXX/ Murphy's Law Calendar 1986 \XXXX/cks@radio.toronto.edu (Chris Siebenmann) (02/24/88)
In article <8802210122.AA12682@jade.berkeley.edu> FATQW@USU.BITNET writes: >Make a new Intuition IDCMP class - HELPKEY. If it's enabled, and the user >presses the HELP key, it sends this class rather than RAWKEY. This way we >won't have to worry about RAWKEY just to see if the user pressed HELP. I would argue against this because it does something that's already easy to do (check for RAWKEY code == 0x5f) and because there are only 31 Intuition message classes possible, and I'd like to preserve as many as possible for future message classes. HELPKEY just doesn't seem important enough (this assumes that the HELP key is guaranteed to generate code 0x5f; if it isn't, then HELPKEY is appropriate). [There are only 31 because Intuition reserves bit 31 for internal use.] -- "I shall clasp my hands together and bow to the corners of the world." Number Ten Ox, "Bridge of Birds" Chris Siebenmann {allegra,mnetor,decvax,pyramid}!utgpu!radio!cks cks@radio.toronto.edu or ...!utgpu!{chp!hak!ziebmef,ontmoh}!cks
FATQW@USU.BITNET (Bryan Ford) (02/29/88)
>>Make a new Intuition IDCMP class - HELPKEY. If it's enabled, and the user >>presses the HELP key, it sends this class rather than RAWKEY. This way we >>won't have to worry about RAWKEY just to see if the user pressed HELP. > > I would argue against this because it does something that's already >easy to do (check for RAWKEY code == 0x5f) and because there are only >31 Intuition message classes possible, and I'd like to preserve as >many as possible for future message classes. HELPKEY just doesn't seem >important enough (this assumes that the HELP key is guaranteed to >generate code 0x5f; if it isn't, then HELPKEY is appropriate). Oops, forgot to mention the *real* reason for doing this! Checking RAWKEY is not hard. However, take a program that uses RAWKEY to pop up context- sensitive help. The user wants to change something in a string gadget. He clicks in the string gadget, and forgets what it's supposed to be used for. He presses HELP. Nothing. He presses it again. And again. Nothing. Panic. He starts pounding and smashing at the keyboard. Still nothing. Get the idea? RAWKEY codes aren't transmitted when string gadgets are activated. I think the user should be able to get help while in a string gadget. And I DON'T want to create my own string gadget support routines. Sorry I forgot to put this in my first posting on this subject. Bryan Bryan Ford //// A computer does what \\\\ Snail: 1790 East 1400 North //// you tell it to do, not \\\\ Logan, UT 84321 \\\X/// what you want it to do. \\\X/// Email: FATQW@USU.BITNET \XXX/ Murphy's Law Calendar 1986 \XXX/