It won't pass certification without a Graffiti shift indicator and there are
no exceptions for this. The user can use Graffiti but the input is
manipulated before it becomes visible - it isn't a text field where what you
write is what you get. entering certain characters do things that aren't
character-oriented. So there is no benefit for capital v. lower case
Graffiti entry - they do the same thing, and neither is drawing a character
on the screen. But there is need to see the shift stroke or the dot
indicator (I don't know the official name for this) so the indicator has to
do be on the screen.
Elia
-----Original Message-----
From: Dan Massey [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 02, 1999 6:55 AM
To: [EMAIL PROTECTED]
Subject: Re: Graffiti/Indicator question
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
