|
That’s a
good, easy interface solution (I wonder who suggested it). However, if we use the * key for VIBS,
what about challenged voters? Use
the # key? Again, that’s an easy
interface (any moron could have thought of it). But then what happens in the future if we have to create a
different kind of conditional voter?
All of the keypad options are used up. We will need to use the arrow keys instead for VIBS,
challenged, and whatever else, and we will have customers that will need to be
re-trained to use the arrow keys for VIBS. Shouldn’t we standardize from the outset using an interface
that allows flexibility for the future (i.e. the arrow keys)? [Footnote
for everyone reading this message on RCR, the aforementioned suggestion to use
the arrow keys was Ken’s. I’m the
moron who thought to use the * and # keys.] How about
this suggestion: Use the < arrow for VIBS, the > arrow for challenged,
the # key to accept, the * key to clear an erroneous VIBS or challenged
setting. Tyler -----Original
Message----- Posted
on behalf of Kerry and Sherry, since Bexar County does not appear to have a
project manager yet. Bexar
wants to use the Spyrus readers, and are going to run VIBS. Here is one
straightforward proposal. When the user hits the * key at the Create?
prompt, a 'V' appears to the left of the prompt, indicating that the card it to
be created for VIBS. Pressing the * key again toggles off VIBS, and the
'V' disappears. Each card insertion resets the state to not-VIBS. This is
complete. 0.2.1 will be ready for testing tomorrow. Ken |