Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Touch-to-correct inserts instead of replacing #17

Open
GoogleCodeExporter opened this issue Apr 10, 2015 · 6 comments
Open

Touch-to-correct inserts instead of replacing #17

GoogleCodeExporter opened this issue Apr 10, 2015 · 6 comments

Comments

@GoogleCodeExporter
Copy link

(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?

Original issue reported on code.google.com by [email protected] on 28 May 2011 at 8:13

@GoogleCodeExporter
Copy link
Author

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, int)

I'm adding a crude workaround to update the selection if it's unable to set the 
composing region.

Original comment by [email protected] on 29 May 2011 at 7:03

@GoogleCodeExporter
Copy link
Author

The workaround made things worse, I disabled it again. Instead, I added a 
warning message toast when turning the option on.

Original comment by [email protected] on 30 May 2011 at 10:40

@GoogleCodeExporter
Copy link
Author

Does not work on Galaxy Tab 10.1.  Honeycomb 3.1.

Original comment by [email protected] on 24 Jul 2011 at 10:36

@GoogleCodeExporter
Copy link
Author

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.

Original comment by [email protected] on 27 Jul 2011 at 1:16

@GoogleCodeExporter
Copy link
Author

I'm done and complete to the T,so fresh and free

Original comment by [email protected] on 6 Apr 2015 at 2:14

@GoogleCodeExporter
Copy link
Author

Free at last

Original comment by [email protected] on 6 Apr 2015 at 2:17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant