Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
09/15/06 19:20
Modified:
  09/15/06 19:24

Read: times


 
#124367 - This isn\'t necessarily true ...
Responding to: ???'s previous message
Neil Kurzman said:
"...

Note if you did not use a diode matrix, you can get ghost keys.
This is when 2 keys are pressed at the same time. The scan may indicate a key is press when it is not. ..."



This is only the case if multiple keys are pressed, as stated. Decades of study have shown that if one waits until the key is released, what one gets is normally the correct key. If the user insists on pressing two keys at once, it doesn't matter anyway, since the result will be wrong in any case. If you're encoding a keyboard, lying on a flat surface and being "touch-typed," then the diodes may be necessary. However, if it's a keypad on the front panel of an instrument, the user is likely to be doing his keypad entry with one finger at a time and actually taking pains to ensure he's pressing the correct key.

The best protection agains inadvertent mistyped data is an "edit" routine which will allow the user to back up and correct the input before sending it to the calling process.

If you don't have any way of echoing the effect of the user's keypad entry, e.g. an LED indicator or an LC Display, such that he can verify/edit it, then, under ALL circumstances, you have a problem. Humans make mistakes. If you launch the nuclear missile or open the airlock on the space station on a blind keypad scan, you will get what you deserve.

RE







List of 27 messages in thread
TopicAuthorDate
Matrix Keyboard not working            01/01/70 00:00      
   the logic            01/01/70 00:00      
   Lots of problems            01/01/70 00:00      
      no, it's completely bad in concept            01/01/70 00:00      
      Does the LCD Work?            01/01/70 00:00      
      enphasizing            01/01/70 00:00      
   commented code            01/01/70 00:00      
      Persistance my friend            01/01/70 00:00      
         I'll try it in other way            01/01/70 00:00      
            I'll make the corrections            01/01/70 00:00      
      Note on comments            01/01/70 00:00      
         bad, very bad - yes, but not necessarily because            01/01/70 00:00      
            Subroutine Details            01/01/70 00:00      
               I don't know            01/01/70 00:00      
                I do not know what that information is good for.            01/01/70 00:00      
                  Column scan after ROW confirmation            01/01/70 00:00      
                     Maybe the problem is not here            01/01/70 00:00      
      more Informative code            01/01/70 00:00      
         Comments are better            01/01/70 00:00      
         The Algorithm            01/01/70 00:00      
            This isn\'t necessarily true ...            01/01/70 00:00      
               a correct pain in the gluteus maximus            01/01/70 00:00      
                  Why so much pain?            01/01/70 00:00      
               An exercise for the student            01/01/70 00:00      
               everyone else            01/01/70 00:00      
   Does the LCD Work?            01/01/70 00:00      
      LCD is fine            01/01/70 00:00      

Back to Subject List