KeyCodes.KEY_ESCAPE

[Antoine Lever]

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");

}

}

});

Please help!

Thank you. 

[Abraham Lin]

The keypress event tends to be handled inconsistently by different browsers/environments:  http://www.quirksmode.org/js/keys.html

As noted in the link above, you should probably stick with keyup or keydown events.

-Abraham

[Thomas Broyer]

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

[Antoine Lever]

Thanks for your help, it's much appreciated.  Below is the code that works for everyone who will spend hours Googling this:

textbox.addKeyUpHandler(new KeyUpHandler() {

@Override

public void onKeyUp(KeyUpEvent event) {

int code = (int) event.getNativeEvent().getKeyCode();

if (code == KeyCodes.KEY_ENTER) {

fp.setText(row, col, tb.getText());

}

if (code == KeyCodes.KEY_ESCAPE) { 

fp.setText(row, col, old);

System.out.println("GOT TO ESCAPE");

}

}

});