On Feb 14, 1:29 am, AB <[email protected]> wrote: > The newish event handler system seems designed to prevent getting a > keycode from the KeyDown and KeyUp events?
You mean a char code? or KeyPress event? > Does anyone know the reasoning behind this? Key down/up events are designed for keys, not chars, contrary to keypress. > This creates a problem. For example, in IE, if one wants to detect > autorepeats of a non char key like an uparrow, you only get it on a > KeyDown event (seehttp://unixpapa.com/js/key.html). Since the > KeyPress does not get repeats (in IE for arrow keys), I need an > KeyDown event handler that knows they key that was hit (maybe i could > write enough logic to first sense the keypress, then remember that > keycode,...) OK, so you seem to really be talking about KeyDown/KeyUp and key code (arrow keys). Have you looked at the events' getNativeKeyCode() method and the KeyCodes class? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/google-web-toolkit?hl=en.
