On 4/21/2010 7:31 AM, jamesc wrote:
The solution is that you shouldn't use onKey() but implement an
InputConnection to handle key presses:
http://groups.google.com/group/android-developers/browse_thread/thread/c800a10de864780d
Just in time :-)
Thanks!
Michael
--
You received this message
The solution is that you shouldn't use onKey() but implement an
InputConnection to handle key presses:
http://groups.google.com/group/android-developers/browse_thread/thread/c800a10de864780d
On Apr 19, 9:52 pm, jamesc jame...@gmail.com wrote:
Perhaps your 'digit2' View doesn't have focus at
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:
Perhaps your 'digit2' View doesn't have focus at the point where input
is being requested?
On Apr 19, 9:15 am, Michael Rueger mike.rue...@gmail.com wrote:
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.
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-
equipped device (even a Hero, which whilst it has 1.5 on it, may help
you track that issues).
When you say that ACTION_UP doesn't work, is this
5 matches
Mail list logo
