Looking for a possible work around to the Korean Keyboard bug - or perhaps I'm not understanding the flow properly.
A normal, English QWERTY keyboard will use the commitText(Char Seq...) method to handle keypressed events. It would seem the Korean keyboard provided by Google likes to send first a setComposingText(CharSeq...) and any following key pressed will also send a commitText(CharSeq...). Example, if I type: "ABC" in my korean keyboard it would call the following methods: // press 'a'... setComposingText(A) // press 'b'... commitText(A) setComposingText(B) // press 'c' commitText(B) setComposingText(C) This isn't consistent with the other keyboards.... any help/ suggestions? -- 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
