If you don't care internally and the case of the letters does not matter,
you may see no benefit, but as a user I may like to write in upper case
and/or lower case, because it's easier to read, etc. The no "added benefit
[for the programmer]" does not seem to be a reason to take the option away
from a user. If a user wants to use all lower case letters they can.
IMO you shouldn't have a GSI in you app if you aren't going to use it.
Placing one on the form and giving it a different behavior is worse than not
having one. I suspect from a user standpoint you should just leave the GSI
and let users write how they want to. If that is not possible, then Palm
does say that they are willing to examine individual cases if you can
convince them that your style change is necessary for your app. If you can
handle all of this info internally already (I assume using a single call to
turn everything lower case.) I doubt you'll convince them.
My $0.02,
Dan
Elia J. Freedman wrote:
>Actually, it is not the character that I care about. It is the display of
>the Graffiti shift indicator that I would like to limit. Internally to my
>app, capital letters are as easy as lower case and I handle both in the
>switch statement. But since there is not "added benefit" for a capital
>letter v. a lower case one, there is no reason to show the Graffiti
>indicator in caps/caps lock mode. So I figured if there was a way to
>"handle" this keystrokes for caps and caps lock and just throw them out,
>that would do.
