🚀 go-pugleaf

In article <8837@ut-sally.UUCP> brian@ut-sally.UUCP (Brian H. Powell) writes:
>In article <1599@apple.UUCP>, tecot@apple.UUCP (Ed Tecot) writes:
>  <Concerning the use of shift-arrow keys...>
>> There is one major problem with that approach:  The user will not be able to
>> use the =, /, *, and + keys on the numeric keypad section of the MacPlus
>> keyboard (as well as the separate keypad that some users have).
>
>     Let me quote from IM-IV, page IV-5.  "If the use of Shift-arrow for
>making selections is more important to your application than the numeric
>keypad, the following paragraphs describe how it should work."  (&c., the
>following paragraphs describe what shift-arrow is supposed to do.)
>
>     First of all, the statement by Ed Tecot is not correct, at least in my
>implementation.  My code only looks at the key-codes if the shift-key is held
>down (and as I mentioned in my previous message, only if the machine I'm using
>has the 64K or 128K ROMs).  On a Mac-Plus keyboard, if the user hits (keypad)
>'*', he gets an asterisk.  If the user hits shift-(keypad)asterisk, he gets
>shift-right-arrow.  On a Mac-Plus keyboard there is some question as to why
>the user would press shift-asterisk on the keypad.

Try again.  Pressing the asterisk on the MacPlus keypad looks EXACTLY like
Shift-Right-Arrow.  Those four keys (=, /, *, +) all force the shift key down.
You cannot distinguish Shift-Right-Arrow, Keypad-*, and Shift-Keypad-* on that
keyboard.  Please try it out before you post.

						_emt