🚀 go-pugleaf

In article <8821@ut-sally.UUCP> brian@ut-sally.UUCP (Brian H. Powell) writes:
>
>     I sent a letter to Apple concerning several topics, one of which was a
>request for any information on how to get the anchor point info out of
>TextEdit.  I got a rather unusual reply, which I think needs some discussion.
> . . .
>     As for the key-codes.  I really doubt they'll stay the same.  But
>somehow, I've got to implement shift-arrow and cmd-shift-arrow, and the 64K
>and 128K ROMs (or is it the keyboard 8021 ROMs?) return certain mathematical
>symbols (consult your numeric keypad) for those keydowns.  (Actually, the
>Mac-Plus works right for cmd-shift-arrow, but not shift-arrow.  The 64K Rom
>macs don't get either right.)  Sooo, my program checks the ROM version number,
>and if it finds a 64K or 128K ROM, it consults the key-code, otherwise it
>takes the event manager's word that the character-code is right.

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).  Why?  Because
there is no way to distinguish a shift-arrow from any of those keys.  This is
done not by the Mac ROMs, but by the keyboard (but no longer true for the
newer ADB keyboards).  My recommendation is to not use shift-arrows; you are
asking for trouble.

						_emt