On Monday, September 10, 2012 5:50:52 PM UTC+2, Antoine Lever wrote:
>
> Could anyone tell me why this code fragment traps the Enter key perfectly
> well but doesn't trap the Escape key?
>
> textBox.addKeyPressHandler(new KeyPressHandler() {
> @Override
> public void onKeyPress(KeyPressEvent event) {
> int code = event.getNativeEvent().getCharCode();
> if (code == KeyCodes.KEY_ENTER) {
> fp.setText(row, col, tb.getText());
> }
> if (code == (char) KeyCodes.KEY_ESCAPE) {
> fp.setText(row, col, old);
> System.out.println("GOT TO ESCAPE");
> }
> }
> });
>
There's a good reason KeyPressEvent reasons in terms of "char codes" (and
more precisely, "printable characters", even though Firefox keeps firing
way too much KeyPressEvents, but with a 0 "char code") and
KeyDown/KeyUpEvent in terms of "key codes".
Also, Firefox keeps treating the the enter key as no producing characters,
such that you'll have a KeyPressEvent with a 0 char code.
See http://code.google.com/p/google-web-toolkit/issues/detail?id=5003
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/y0q3Ul5yxn4J.
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.
