As an Android user not developer, maybe this explains a somewhat annoying
aspect of some Andorid apps which, when you open them, position the cursor
in a field which requires input before you can continue but does not bring
up the keyboard until you tap on the field.
Pete
On Thu, Mar 15, 2012 at
> I am happy to report that all three approached work. The keyboard stays
> hidden until the field is touched. Enter some data with the keyboard, switch
> focus to another field, touch the initial field, focus switch and keyboard
> comes back up. All seems normal.
>
> However I think I f
I am happy to report that all three approached work. The keyboard stays hidden
until the field is touched. Enter some data with the keyboard, switch focus to
another field, touch the initial field, focus switch and keyboard comes back
up. All seems normal.
However I think I found a bug.
The other way, which I have used for some time, is to group the field (either
in a group by itself, or including all the fields you don't want to
automatically get focused) then set the group's traversalOn to false.
-- Peter
Peter M. Brigham
pmb...@gmail.com
http://home.comcast.net/~pmbrig
On
On 3/14/12 2:09 PM, Michael Doub wrote:
Is there a way to detect that the user has closed the keyboard on
Android?
Maybe someone can point out an appropriate technique to solve my
problem. I have a card with one editable field on it. When I go to
that card currently the focus immediately go to
Is there a way to detect that the user has closed the keyboard on Android?
Maybe someone can point out an appropriate technique to solve my problem. I
have a card with one editable field on it. When I go to that card currently
the focus immediately go to that field and the keyboard pops up.
