|
Originally Posted by WolverineJon
|
I have a couple of questions relating to text input via the built-in Block Recognizer method. (I'm using a Dell Axim x30.)
(1) Sometimes when I'm entering text a character I've entered is misinterpreted as the "punctuation" tap -- the little dot appears in the corner of the Block Recognizer area, and the next character I enter is interpreted as a punctuation mark. Is there a way to cancel the "punctuation" state that's quicker than entering any character and then backspacing it (two separate pen strokes)?
(2) A common character misrecognition that I encounter when entering text is one of the standard 26 letters (a through z) being misinterpreted as the œ ("oe") character. Is there a way to force Block Recognizer to only interpret input as one of the standard 26 letters when entering letters and not in one of the "shift" modes?
Thanks in advance!
|
Well, I accidentally happened upon the answer to one of the two issues! Regarding cancelling shift state, I found that the shift state applies only to either the "letters" section of the input area or the "numbers" section, but not both at once. So if the letters section is in shift state, it can effectively be cancelled by tapping once in the numbers section to put that section into shift state (thus taking the letters section out of shift state).
I also found that the original Grafitti app allows a backspace character to be entered to cancel the shift state (as can be seen here:
http://www.palm.com/us/products/input/); unfortuantely, Block Recognizer treats a backspace pen stroke as a "-" character while in shift mode. It would be nice if this were fixed in a future Block Recognizer update, since this method of cancelling the shift state seems to be much more intuitive, as well as faster to perform.