I've just started to try and configure WS/Nexus to use hotkeys.

In particular, I want to use CTRL-ALT-SHIFT plus either N or T to activate either of two Nexus docks.

The problem is, when I press these keys - with any application running - they don't seem to be intercepted by WS or Nexus. I can press them till the cows come home, but nothing happens.

If I press the keys with, say, Firefox active, it immediately thinks I'm searching for that character (? for ctrl-shift-alt-n). I've tried both alts, both shifts, and both ctrls (6 combinations), but there ain't no way WS is seeing these keys.

This is with WS set to "hidden" - lowest z-order, so I'm not sure if that's what's causing this, or if it's related... but I just reset WS to top z-order, etc, and that didn't work either.

I'm using an IBM SK-8815 board with and without the IBM key handler software loaded, and it makes no difference.

The ONLY other application that looks for hotkeys is Clipcache plus 2.9, but I disabled that and I still can't seem to activate WS.

Luckily, the nexus docks ignored the "ignore mouseover" setting, otherwise I would have been up the proverbial creek.

Any ideas or suggestions?

FWIW, I'm really surprised that Winstep doesn't trap the win key - that is the single most useful key on the whole keyboard, from my perspective. Is this by design, or you don't want to add yet another application to the winkey trapping chain?

My fault, sorry. There is a bug in the NeXuS activation hotkeys that prevents them from working. Fixed for the next version, but when it comes out you will need to reset the hotkeys.



Shelf hotkeys, on the other hand, are working perfectly. Maybe you're mixing NeXuS hotkeys with Shelf tab hotkeys?



MSDN clearly states that the WIN key is reserved for Operating System use.

Thanks Jorge, at least I know my mind isn't melting...
WS does trap the hotkeys fine, I'm sorry for not being clear about the application I was targeting... NS/WS/NX/WX...

Don't you just love MS "reserving" and "recommending" keyboard configurations... I use 3 different products that all trap and use the windows key, and even MS only use it for "usability" "enhancements". Pah.

If you ever do decide to modify any of the tools to check a registry entry for an activation that might "accidentally" be set to the "win" key, I wouldn't mind...