We don't have any plan on adding that. An IME being visible can mean anything from a small bar along the bottom to it covering the full screen of your UI. An API telling whether it is visible or not is just not sufficient for this. The intended way for this to work is for the underlying application to be resizeable and do the appropriate thing for whatever size it gets. Also this is really an independent issue from different devices -- the input method system is pluggable, users can download and use whatever input method they want, so even if there was only ever one device running Android applications still need to deal with input methods that work in very different ways.
On Tue, Sep 22, 2009 at 5:20 AM, Lee <[email protected]> wrote: > > Thanks > > A recommendation that I'd make for a future rev of the API is that it > be possible to register a callback interface to indicate when an IME > is activated or deactivated. > > I've read various statements that it's not good practice to trigger > off an IME transition but for our app it's a pretty essential feature > because we aren't interacting with local input controls at all and we > need to provide a UI to both show the IME (simple) but also we need to > be notified when the IME is no longer active. > > This is where Android development is going to get complicated. > Applications that work great on the G1 or the emulator look and behave > totally differently on other platforms, so although we're developing > for a base system the UX is going to potentially be very different > depending on the phone. Having additional interfaces like this would > allow us to reduce some of these impacts. > > Thanks > Lee > > On Sep 22, 6:24 pm, Dianne Hackborn <[email protected]> wrote: > > 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. > > > -- 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 -~----------~----~----~----~------~----~------~--~---
