🚀 go-pugleaf

mdm@wdl1.wdl.loral.com (Mike D Marchionna) writes:

>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.

Bravo, I will say my BIGGEST gripe to date is the lack of documentation. Maybe
someone out there thinks that it is just common sense, but I will gladly admit
ignorance just to get answers. Here is the frosting on the cake. About 
everything I look up is MENTIONED but there is no detailed documentation. I
have spent some considerable time working with exception code and have had to\
work out the specs by trial and error. ARRRRGGGGHHHHH!