Removing the shift indicator isn't good because, you are right, the user
will still need to see the other indicator cases.
It really is a stupid little thing, but the shift indicator when it is upper
or caps lock case interferes with some of the layout, where the dot and
slash modes do not. Since the interfering cases aren't pertinent, I thought
I would get rid of them. Of course, it is probably more work than it is
worth and isn't that big a deal. Thank you Keith and Daniel for the input.
I will try your method, Daniel.
Elia
-----Original Message-----
From: Kenneth Albanowski [mailto:[EMAIL PROTECTED]]
My first thought is to remove the shift indicator (no matter what the
platinum guidelines say). But that won't work, as punctuation and extended
shift presumably will make a difference to your app.
Personally, I don't see this as a major deal. Someone can turn on
caps-lock, true, but I doubt they'll view that as some special mode. (This
depends on your program, of course.) I'll agree that a forcing condition
(through the removal of the case-shift UI) would be appropriate here, but
I also feel it's reasonable to expect the user to assume that the visible
upper-case shift state is merely related to the normal character-entry
mechanism, and does not imply any specific contract with the program for
special use of upper-case characters.
