Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Fix a Sticky Keys/Quickeys display conflict Apps
I keep the Sticky Keys feature of Universal Access enabled at all times. They are handy, don't change the way I normally operate, and when giving lectures, the 'Display pressed keys' feature allows students to see what modifiers I use.

I also use Quickeys, which allows you to string a combination of keys together for a shortcut, like Command-Option-K then 'F' then 'S' to connect to a file server. This lets you define a whole bunch of Command-Option-K shortcuts. Quickeys also displays the modifiers on the screen.

Problem: When used together, pressing Command and Option is displayed by the system, then taken over by Quickeys. The system never sees the release, and the display (just the display) of the modifier keys stays on. You have to press the key three times to rotate through on, locked, then off. You can't turn off that option in Quickeys, or it won't do a string of modifiers. I tried turning off the display option in the Universal Access System Preferences panel, but then you get a sticky key and don't know it.

Solution: Press the modifier keys consecutively (which is how Sticky Keys is supposed to work). Press Command-Option, then release them, then press K, etc.. The system turns the display off when Quickeys takes over.

This is pretty obscure, and only annoying, but I was happy to find a solution.
  • Currently 2.25 / 5
  You rated: 4 / 5 (8 votes cast)

Fix a Sticky Keys/Quickeys display conflict | 2 comments | Create New Account
Click here to return to the 'Fix a Sticky Keys/Quickeys display conflict' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Fix a Sticky Keys/Quickeys display conflict
Authored by: guns on May 14, '09 10:58:00AM

So QuickKeys is like emacs for the GUI? Very interesting.

[ Reply to This | # ]
Fix a Sticky Keys/Quickeys display conflict
Authored by: dcottle on Sep 05, '09 07:23:03AM

I recently upgraded to the latest version, and they have apparently fixed this issue.

[ Reply to This | # ]