Thanks Dianne, I now seem to be getting somewhere using addTextChangedListener() instead of setOnKeyListener().
Regards On May 21, 6:50 pm, Dianne Hackborn <hack...@android.com> wrote: > If you are having this text put into an EditText, there are all kinds of > APIs on that to get callbacks when the text is modified. I would strongly > recommend using those instead of any kind of raw event interception: keep in > mind that there will be future devices with all kinds of keyboard > configurations, using various key sequences to generate the actual > characters (think 12 kit, 1/2 qwerty, etc) so unless you are using the full > key character map class you likely not work there either. > > If you leave your UI without an EditText in focus, the user can long press > on the MENU key to force the soft keyboard to be displayed (or you can call > the API to show it yourself), and then you are in the situation I already > described: no InputConnection, so text coming from the IME is turned into > raw key events, with lower fidelity support of IME features, but > compatibility with existing apps that are looking for key events. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
