Re: Facing some problems after switching to GWT 2.1 from GWT 2.0.4

2010-12-21 Thread Casey
I too was using KeyPressEvent in 2.0.4 and it was working perfectly but when I upgraded to 2.1.1 it stopped working. Based on Brian Reilly's comment I changed the event to KeyDownHandler and the comparison to event.getNativeKeyCode() == RETURN_KEY and it's back to working again. So even though the

Re: Facing some problems after switching to GWT 2.1 from GWT 2.0.4

2010-12-21 Thread Thomas Broyer
Let me re-state it (once more): there was a bug in versions before 2.1.0, where you couldn't tell whether the user pressed the down arrow or the left parenthesis (or something like that). GWT 2.1 fixes that bug, but then it exposes a more low level behavior where you directly get what the

Re: Facing some problems after switching to GWT 2.1 from GWT 2.0.4

2010-12-03 Thread dominic jansen
hi aditya, i ve noticed that there are different behaviours for the KeyPressHandler for each browser (e.g. for me the safari browser did not recognize the keypressevent). maybe you can use the KeyDownHandler or KeyUpHandler instead of the KeyPressHandler. this worked for me best, dom

Re: Facing some problems after switching to GWT 2.1 from GWT 2.0.4

2010-12-03 Thread aditya sanas
hi dominic, I m receiving key press event in all the browser the thing that i have noticed which doesn't work in GWT 2.1 is - *if(event.getCharCode()==KeyCodes.KEY_ENTER){ * the o/p of event.getCharCode() in GWT 2.1 is nothing not even 0 so i cnt compare it with KeyCodes.KEY_ENTER i had

Facing some problems after switching to GWT 2.1 from GWT 2.0.4

2010-12-02 Thread Aditya
Hi, I have updated my GWT version to 2.1 and faced some of the problems regarding textbox' key press handlers... the code which works completely fine in previous version is txtPassword.addKeyPressHandler(new KeyPressHandler() { @Override