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.

Bad predictions

OKK77
Cool. Back-up/restore from sd will be a good feature.

Ok, I have two more queries/reports:

1. The default suggestion is a longer version of the intended word. Example: type "expec" and it will default "expected" instead of "expect". Is it intended?

2. If I mishit and type "tine" instead of "time", "tine" is the default suggestion. While "tine" is a valid word in the dictionary, I suspect most people will be typing "time" at orders of magnitude more than "tine". :)
cyril Developer
These 2 questions have the same answer: the algorithm suggest the word with the highest frequency in the dictionary (it's a bit more complex than that but that's the idea) except if the typed word is valid; in that case it suggests the typed word. I wanted to changed this behavior once (not suggesting the typed word) and the result was awful. The only solution is to add an AutoText "tine -> time", which is something I can do in a future release
OKK77
Oops, mistake in the first point. It was supposed to be:

Typed: "expec".
Suggested: "expected".
Wanted: "expect". :)

Anyway, I was trying those out with stock keyboard. Behaviour for tine/time is the same. I just gotta live with it, I suppose. For "expec", default will suggest "expect" instead of "expected".
davieboynj
when i type in "understant" on SKB it lists no suggestions and does no auto correction, when i use the default htc keyboard it auto-corrects to "understand". I'm sure it happens with other words, but this is a functional example of something that doesn't work right. Couple that with SKB thinking that two presses in rapid succession across the keyboard are a swipe, and i really can't work with this keyboard. its faster in most circumstances, but less predictable. I'm returning for a refund, but will keep my eyes on the site for updates, as i'm really impressed with SKB, but its just not there yet.
cyril Developer
"d" and "t" are too far away, that's why this correction cannot work
As for the swipe, I will try to do something, but the issue is that if you press two letters a specific timing, the keyboard really receives exactly the same events as it would receive for a swipe...