shaffer-squeak at cs.westminster.edu writes:
 > 
 > I've been delving around in the depths of keystroke processing and I
 > noticed something in EventSensor>>primKbdPeek that has me stumped (3.6
 > image).  The method seems to have two loops (I don't know why but I'm
 > not sure if that's my question), the first looks at keyboardBuffer
 > which was filled with keycodes that have the key qualifier (ctrl, alt
 > etc) masked onto the upper 4 bits of 12.  The second loop, however,
 > looks directly at the event queue and returns evt at: 3 which appears
 > to be the raw keycode.  I have no idea if this second loop ever
 > executes...but if it does, is it right?  If a tree falls in the
 > woods...well, anyway, I'm just trying to understand the how
 > ParagraphEditor gets its key codes and this seems like an important
 > part.
 > 
 > David
 > 
 > 


Forget it, no matter what the bits get stripped off by
InputSensor>>characterForKeycode:, one of only two senders (the second
is just checking for existance of the character) so the inconsistency
doesn't really seem to impact anyone.

David Shaffer
cdshaffer at acm.org