🚀 go-pugleaf

andrew@cubetech.com writes:

>In article <1992Oct24.184745.19341@prim> dave@prim (Dave Griffiths) writes:
>>Just to lob the ball back into NeXT's court: there must have been something
>>lacking either in the documentation or the interface to make developers
>>_want_ to interpret raw scan codes.

>No.  NeXT provides a way to get what the user types without going down
>to the metal.  While there are often reasons for breaking the rules,
>this was not one of them.  It sounds like a case of one more thing
>that is buried just a bit too deep in
>/NextLibrary/Documentation/NextDev (there is a lot of stuff in there...).

So enlighten us all already!  Everybody is talking about what a shame it
is that all these dumb developers didn't use the approved (portable) method
to interpret keyboard input, but nobody has said where it's documented
or shown how it's done.  So out with this big secret already.

--MDM

-- 
 _________________________________________________________________________ 
(  _______________________________   Brain, and brain!  What is brain!    ) 
 \________________________________)        --Star Trek (Spock's Brain)   /
El_Rayo_X_______________________________________________________________/