🚀 go-pugleaf

In article <1992Oct27.160053.17974@cs.mcgill.ca> samurai@cs.mcgill.ca (Darcy  
BROCKBANK) writes:
> In article <1992Oct24.142015.21925@splunge.uucp> royce@splunge.uucp (Royce  
Howland) writes:
> >dave@prim (Dave Griffiths) writes:
> >
> >It's certainly possible that NeXT didn't document things clearly enough,
> >but in the case of the keyboard scan-codes example, one doesn't need to
> >be a rocket surgeon to realize that there are probably other, more secure
> >ways for an app to get keyboard input than reading the raw scan codes,
> >whether one suspected ADB was coming or not.  Going to the hardware on
> >any machine of this level of complexity is always a risk.
> 
> All fine and dandy, but I still don't know what the "blessed: way
> of doing it is, and any mention of it in the docs is non-existent.
> 

Once again:  look at _NeXTSTEP Concepts_, Chapter 5 ("Events"), the section  
labelled "Keyboard Information". This is the section in the documentation  
talking about how to handle and interpret keyboard events, including how to  
distinguish where keys came from w/out resorting to scan codes. Has anyone here  
actually bothered to read this section? :-)  ..bruce..

-------------------------------------------------------------------------------
Bruce F. Webster             |  I have seen the Altair live and die
CTO, Pages Software Inc      |  And software startups score on sorry score--
bwebster@pages.com           |  And millions made by men like Mitch Kapor.
#import <pages/disclaimer.h> |            -- Jeff Duntemann
-------------------------------------------------------------------------------