You can use this to indicate how the application should be positioned behind your IME: http://developer.android.com/reference/android/inputmethodservice/InputMethodService.html#onComputeInsets(android.inputmethodservice.InputMethodService.Insets)
On Sat, Aug 4, 2012 at 12:35 AM, yakobom <[email protected]> wrote: > Hi Dianne, > "If you design it to be floating so that it doesn't impact app content, > you can easily put it anywhere" - can you please explain how can I do that? > And, is it possible to design it so this mode will be dynamically > switchable? (Meaning, the user will be able to switch between the floating > and the pushing modes) > > Thanks, > yakobom > > > On Wednesday, August 1, 2012 7:14:50 PM UTC+3, Dianne Hackborn wrote: >> >> In the current platform your IME UI can only push app content up from the >> bottom of the screen. If you design it to be floating so that it doesn't >> impact app content, you can easily put it anywhere (if nothing else make >> the window fill the entire screen and leave all the parts transparent >> except where you want to draw your UI), but if you want apps to adjust >> their UI to accommodate the only option is to have their content shift up >> from the bottom. >> >> On Wed, Oct 13, 2010 at 2:02 PM, Saied <[email protected]> wrote: >> >>> Hello, >>> >>> I am a developer and recently completed the implementation of my >>> keyboard MessagEase. It's available on the Market (with its very- >>> different features, making it quite unlike QWERTY). >>> >>> This keyboard works fine as a replacement of the standard keyboard on >>> an Android Phone. But for a An Android Tablet, it would work best if >>> it's implemented as a floating, movable keyboard. >>> >>> (the footprint of this keyboard is mostly dependable on the size of a >>> human's finger; it remains the same even if the tablet's display is >>> much larger than a phone's. Therefore it'll take a relatively smaller >>> area on a tablet.) >>> >>> If I use the current SDK hooks, it will have to take a significant >>> portion of the screen, defeating the purpose. >>> >>> Can someone point me to the right direction in creating a floating >>> keyboard? or is it possible? >>> >>> Thanks. >>> >>> Saied Nesbat, >>> Exideas (creator of MessagEase) >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Android Developers" group. >>> To post to this group, send email to android-developers@** >>> googlegroups.com <[email protected]> >>> To unsubscribe from this group, send email to >>> android-developers+**[email protected]<android-developers%[email protected]> >>> For more options, visit this group at >>> http://groups.google.com/**group/android-developers?hl=en<http://groups.google.com/group/android-developers?hl=en> >>> >> >> >> >> -- >> 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 > -- 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
