Archived forum. This is a read-only copy of the Smart Keyboard community forum (2010–2015), kept for its history and its skins. Posts are shown as they were written, so some answers are out of date — see Help for current information. Want a post of yours removed? Email contact@smartkeyboardpro.com.

Touch to correct problem on longer texts

SaKeygo
Hi, just want to say how much I'm continuing to enjoy using SmartKeyboard. The updates and new features have been really great. One bug I did notice is that the touch-to-correct feature seems to stop working when a text is of a certain length.
For example, if you copy the following list - the touch-to-correct will no longer work at about the 22nd line.

01. This is a test of Smart Keyboard touch to correct.
02. This is a test of Smart Keyboard touch to correct.
03. This is a test of Smart Keyboard touch to correct.
04. This is a test of Smart Keyboard touch to correct.
05. This is a test of Smart Keyboard touch to correct.
06. This is a test of Smart Keyboard touch to correct.
07. This is a test of Smart Keyboard touch to correct.
08. This is a test of Smart Keyboard touch to correct.
09. This is a test of Smart Keyboard touch to correct.
10. This is a test of Smart Keyboard touch to correct.
11. This is a test of Smart Keyboard touch to correct.
12. This is a test of Smart Keyboard touch to correct.
13. This is a test of Smart Keyboard touch to correct.
14. This is a test of Smart Keyboard touch to correct.
15. This is a test of Smart Keyboard touch to correct.
16. This is a test of Smart Keyboard touch to correct.
17. This is a test of Smart Keyboard touch to correct.
18. This is a test of Smart Keyboard touch to correct.
19. This is a test of Smart Keyboard touch to correct.
20. This is a test of Smart Keyboard touch to correct.
21. This is a test of Smart Keyboard touch to correct.
22. This is a test of Smart Keyboard touch to correct.
23. This is a test of Smart Keyboard touch to correct.
24. This is a test of Smart Keyboard touch to correct.

I'm using an HTC Evo, running 2.3.3, although I noticed this before the update as well. Don't know if this is affecting anyone else.