Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!gatech!bloom-beacon!think!ames!sdcsvax!jww From: jww@sdcsvax.UCSD.EDU (Joel West) Newsgroups: comp.sys.mac Subject: Re: Anchor points and Arrow keys (actually keyboards) Message-ID: <3481@sdcsvax.UCSD.EDU> Date: Sat, 18-Jul-87 00:48:43 EDT Article-I.D.: sdcsvax.3481 Posted: Sat Jul 18 00:48:43 1987 Date-Received: Sat, 18-Jul-87 19:13:32 EDT References: <19741@ucbvax.BERKELEY.EDU> <8503@ut-sally.UUCP> Organization: Palomar Software, Inc., Vista, CA Lines: 15 Summary: Keyboards are fixed In article <19741@ucbvax.BERKELEY.EDU>, oster@dewey.soe.berkeley.edu (David < 1.) Thanks to Apple for fixing the keyboard! On a MacPlus, the shifted < arrow keys produce an EventRecord identical to the ones produced by < *,\,-,= on the numeric keypad. On the Mac SE and MacII, the shifted < arrow keys produce an EventRecord identical to the un-shifted arrow < keys (same ascii and keycode), but the shift bit is set in the < modifiers field of the EventRecord. This is just the right thing. Actually, I think this is fixed on System 4.1 and the Plus, which has the new _KeyTrans trap used for the ADB keyboards on the SE and II. In MPW 2.0b1, command-up-arrow and command-shift-up-arrow have distinct meanings and they both seem to work. -- Joel West, Palomar Software, Inc. (c/o UCSD) {ucbvax,ihnp4}!sdcsvax!jww or jww@sdcsvax.ucsd.edu