i found out that the proximity prediction is related to how close to the correct letter than you're pressing. the algorithm tries to predict the likelihood of the key that you pressed is the one that you intended to press. so if you type "bua" and the "a" has been stuck more towards the left, the algorithm will suggest "bua" because it thinks that the "a" is the one you intended. but if you try it again and press "a" slightly towards the "s" then the likelihood of a mistype is represented higher so it suggests "bus".OKK77 wrote:One strange thing I observed right now:
I was typing the word "bus" and hit "bua". It was not able to predict it at first. So, I deleted the "a" and typed "s". The next "bus" I typed, it predicted fine. "bua" and "bus" were shown and "bus" is highlighted.
The same phenomenon was observed when I typed "wanting" as well.
so when i first suggested a proximity prediction problem i did not know this. i've been making a concerted effort to type more "cleaner". a possible solution would be to implement a larger radius for the algorithm to suggest keystrokes. but this obviously may increase the chance that suggestions would be wrong.
or perhaps a spell checker would fix this problem.
we'll see what goodness cyril has in store for us.