Touch-to-correct inserts instead of replacing
Brought to you by:
starssoft
Menu
▾
▴
#17 Touch-to-correct inserts instead of replacing
Accepted
nobody
None
Medium
Defect
2011-07-26
2011-05-28
Anonymous
No
Originally created by: Klaus.We...@gmail.com
Originally owned by: Klaus.We...@gmail.com
(reported in a Market review)
What steps will reproduce the problem?
1. Turn on "Touch to correct" in options
2. Type "Th is a tes"
3. Touch the misspelled words to correct them to "This" and "test"
What is the expected output? What do you see instead?
On some systems, the correction is inserted instead of replacing the typed word.
Appears to work correctly on Xoom (Honeycomb) and Nexus S (Gingerbread), possibly an issue on Froyo systems only?
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
The Gingerbread keyboard's recorrection depends on an API method that didn't exist in earlier versions:
[http://developer.android.com/reference/android/view/inputmethod/InputConnection.html#setComposingRegion(int](http://developer.android.com/reference/android/view/inputmethod/InputConnection.html#setComposingRegion(int), int)
I'm adding a crude workaround to update the selection if it's unable to set the composing region.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
The workaround made things worse, I disabled it again. Instead, I added a warning message toast when turning the option on.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: peterwri...@isky.co.za
Does not work on Galaxy Tab 10.1. Honeycomb 3.1.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
About comment #3, can you please be more specific about the behavior you're seeing? Do you have "touch to correct" switched on in settings? The original bug was about recorrect on pre-Gingerbread devices, this shouldn't affect a Honeycomb device.