On 4/18/2010 3:43 PM, jamesc wrote:
Hi Michael
It'll be the Sense UI's IME which has different behaviour to the stock
Android IME. Sadly, I'd suggest that you get your hands on a Sense UI-
Thanks for the hint, I found this issue for the problem:
http://code.google.com/p/android/issues/detail?id=2882&q=htc%20ime&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
equipped device (even a Hero, which whilst it has 1.5 on it, may help
you track that issues).
I'm afraid so...
When you say that ACTION_UP doesn't work, is this for all key presses,
or just some in particular? A bit more information on what you're
attempting to capture with ACTION_UP would be helpful in order to
allow to to get some useful debug prints out.
See code below, very simple one digit entry fields. (any tips for
achieving that more elegantly appreciated :-) ). On the HTC the focus
doesn't move to the next field on a key press (the user tells me), so
I'm assuming somehow the key event doesn't make it.
Michael
digit2.setOnKeyListener(new View.OnKeyListener() {
@Override
public boolean onKey(View v, int keyCode, KeyEvent event) {
if (event.getAction() == KeyEvent.ACTION_UP) {
if (event.getKeyCode() == KeyEvent.KEYCODE_DEL) {
digit1.requestFocus();
} else {
digit3.requestFocus();
}
}
return false;
}
});
--
You received this message because you are subscribed to the Google
Groups "Android Developers" 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/android-developers?hl=en
