OK Dianne, thank you for highlighting that the soft keyboard is not a software keyboard. For me that is a novel insight, as I had hoped and expected that the IME was (also, at the very least) meant to simply emulate a software keyboard. Apparently it acts more like a newly defined virtual input peripheral then. Indeed a paradigm shift for me, as I simply want to keep on responding to individual key presses and nothing else.
It would be absolutely fabulous to find some minimal example code of how to do just that - and only that - with the IME. The soft keyboard SDK sample is rather intimidating with its hundreds of lines of code for a rich editing interface, making it hard to extract minimum code as needed for just capturing individual key presses. I think other developers would also appreciate this. Thanks! On May 21, 10:43 am, Dianne Hackborn <hack...@android.com> wrote: > It's not a software keyboard, it is an IME with a rich editing interface > back to the text editor, including things like showing candidates, > performing replacement, etc. For example, as you enter a word, each key you > enter is actually the IME delivering to the editor a new candidate text > string to replace the one currently displayed. This is actually a pretty > typical IME interface. > > It is certainly not a design oversight... though you can simply not give > the IME an InputConnection, in which case it falls back on delivering raw > key events (when it can... for some characters it simply won't be able to) > and gives the user a crummy editing experience. --~--~---------~--~----~------------~-------~--~----~ 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 To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
