GNOME Bugzilla – Bug 516321
Caps lock not correctly reporting the state when toggled
Last modified: 2008-07-22 19:33:52 UTC
As reported by Steve on the Orca list, we now always say caps lock is "on" when it is toggled on and off. Daniel Dalton since narrowed it down to the triple click uber patch. (Thanks Daniel!!) Patch to follow.
Created attachment 105190 [details] [review] revision 1 This seems to do the job for desktop layout and still allows one to bind/rebind and use single and multi-click Caps Lock commands in laptop layout. Please test.
(In reply to comment #1) > Created an attachment (id=105190) [edit] > revision 1 > > This seems to do the job for desktop layout and still allows one to bind/rebind > and use single and multi-click Caps Lock commands in laptop layout. Please > test. > This seems to do fine. In looking at the patch, I see that pyatspi.MODIFIER_META and pyatspi.MODIFIER_NUMLOCK are also missing. So, I'm guessing getting rid of NUMLOCK is intentional since it is so poorly behaved, but META was also an accident similar to SHIFTLOCK.
Created attachment 105366 [details] [review] Patch to add META as well and also adjust comment Seems to work OK. Will run with the gtk-demo regression tests in a bit.
(In reply to comment #3) > Created an attachment (id=105366) [edit] > Patch to add META as well and also adjust comment > > Seems to work OK. Will run with the gtk-demo regression tests in a bit. > The gtk-demo regression tests work well, it pylints to a 10.0. CapsLock works, and I can rebind keys to use the Meta key (e.g., the "Windows" key). I say commit if you think it's good.
Thanks Will. Patch committed. Moving to pending.