You are right, I'll see what of either is the case. Is turns out there are quite a few options to map ascii chars to keyboard code. E.g. \n and \r could map to enter, ^M or ^L (and maybe more). And even when it seems okay with one application, an other might not respond as expected....
Joep 2011/12/22 Oliver Seitz <[email protected]>: > I have no clue about that file in general, but line 745 looks suspicious to > me anyway: > > 0x2D | ASCII_USB_CTRL | ASCII_USB_CTRL, ; 0x1F control-_ > > Either one of the "ASCII_USB_CTRL" is wrong or redundant. > > Greets, > Kiste > >> Modified: >> /trunk/include/peripheral/usb/usb_keyboard.jal > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/jallib?hl=en. > -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
