I think you're using inverse logic here. Especially
since your app handles characters of either case.
Instead of thinking "there's no added benefit
to showing case" think "there's no harm in
showing case".
Save yourself the work and leave the case indicator
alone.
Or, you could challenge the rule that requires
the case indicator for certification. Make your
case (no pun intended) to 3Com.
But really, if it doesn't affect the operation
of your program to allow lowercase & uppercase,
just let it be.
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi./sec ... not just a good idea, it's the LAW!
> -----Original Message-----
> From: Elia J. Freedman [mailto:[EMAIL PROTECTED]]
>
> 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.
