workaround for broken numlock support?
workaround for broken numlock support?
- Subject: workaround for broken numlock support?
- From: Daryn <email@hidden>
- Date: Mon, 7 Apr 2003 02:13:31 -0500
Enabling the numlock will cause all subsequent non-keypad key events to
have NSNumericPadKeyMask set in the event's modifierFlags -- UNTIL a
real keypad key event is generated, then the flag is cleared for
non-keypad key events.
This appears to broken and buggy behavior. The numlock should have its
own distinct modifierFlag. My immediate issue it that I cannot discern
a KP1 from a numlock-enabled 1 w/o divining the keyCode. Am I
overlooking something obvious?
So how do I workaround this bug? I can use flagsChanged: to watch for
NSNumericPadKeyMask generated by the numlock to track its status. The
problem is how to "fix" the non-keypad key events that erroneously have
the NSNumericPadKeyMask set. Is there a clean way to regenerate a key
event from just a keyCode?
I'd almost be willing to use Carbon as a workaround. Any advice would
be greatly appreciated.
Daryn
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.