You find out about the IME impacting your application by your application
window getting resized.  That is the -only- way.  Different IMEs may have
radically different approaches to interacting with the user.  You certainly
can't assume they are doing anything solely or at all with the back key.
This has nothing to do with different vendors, it applies to any IME the
user may install as well.

On Mon, Sep 21, 2009 at 11:55 PM, Lee <[email protected]> wrote:

>
> I've been testing my application on a HTC magic and it's incompatible
> with the keyboard that ships with the magic.
>
> My application allows the on-screen keyboard to be displayed when the
> user clicks on icon on the screen.  When using the emulator the way
> that I determine that the keyboard has been hidden is through
> responding to the KEYCODE_BACK keyevent.
>
> On the HTC keyboard there is an additional key that allows the
> keyboard to be hidden.  When this key is pressed the keyboard is
> hidden but no KeyEvent is sent to the application with the result that
> the application is now out of sync with the keyboard state.
>
> In general is there a way to detect software keyboard hide / show
> events in a non-vendor specific manner? This would be highly useful
> for any application that is implementing custom views.
>
> Thanks
> Lee
> >
>


-- 
Dianne Hackborn
Android framework engineer
[email protected]

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to