After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 107261 - Need SPI_KEYMASK_NUMLOCK
Need SPI_KEYMASK_NUMLOCK
Status: RESOLVED FIXED
Product: at-spi
Classification: Platform
Component: api
unspecified
Other All
: High enhancement
: ---
Assigned To: bill.haneman
bill.haneman
Depends on:
Blocks:
 
 
Reported: 2003-02-28 15:17 UTC by bill.haneman
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description bill.haneman 2003-02-28 15:17:08 UTC 
We need some way to refer to "virtual modfiers" such as NumLock, since on
some keyboards NumLock is "MOD2" and on others it seems to be "MOD3".  

At the moment the workaround is to listen for both and assume that one or
the other is NumLock, but that will clearly cause problems if the "other"
modifier is actually used on the keyboard in question.
Comment 1 bill.haneman 2003-03-13 14:05:55 UTC 
well, relatively easy fix... I am marking it easy-fix so we don't
entirely ignore it.
Comment 2 bill.haneman 2003-04-04 16:30:30 UTC 
this is blocking some Java work/workarounds, so raising the prio.
Comment 3 bill.haneman 2003-04-10 11:48:43 UTC 
Fixed in CVS: clients can now register for key events with mask
SPI_KEYMASK_NUMLOCK, and can check for the equivalent bit in the
keyboard:modifiers event detail return values.