Win32: caps-lock and num-lock generate too many KeyEvents

XMLWordPrintable

    • generic
    • windows_95

      The AWT has been recently spec'd on how Caps-Lock and Num-Lock keys fire events: when a modifier is turned on a KEY_PRESSED is sent, and when it is turned off a KEY_RELEASED should be sent. Applications can determine the state of these modifiers by remembering the last KeyEvent fired with that keyCode.

      On Win32, KEY_PRESSED is sent when the key is pressed, and KEY_RELEASED when
      the key is released. This doesn't reflect the current state of the modifier.

            Assignee:
            Eric Hawkes (Inactive)
            Reporter:
            Tom Ball (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: