I think having shift configured as a movementhotkey when sending to a wow window other than main would fix the problem. Is there any way to prevent shift from being seen as a modifier, and simply using it as a standard movement hotkey?
I think having shift configured as a movementhotkey when sending to a wow window other than main would fix the problem. Is there any way to prevent shift from being seen as a modifier, and simply using it as a standard movement hotkey?
hi, as far as i know, this is not directly possible as shift is predifiened as modifier and therefor can'T be used as a hotkey allone.
Only workaround i could imagine is defining a other key as an movement key and letting it broadcast shift like:
Code:<MovementHotkey y> <SendLabel w1,w2> <Key shift>
OLIPCS - ordinary life is pretty complex stuff
----------------------------------------------------------------
Olipcs is right. Just to clarify, the restriction is that Shift can't be used as a trigger by itself. This restriction has no effect on output. Hotkeys can take any action you like including sending Shift by itself.
I made this restriction to try to prevent certain user errors. I'm planning to remove it before the end of the beta.
Please let me know if Olipc's Y hotkey solves the problem. If so I'll raise "removing the restriction" up higher on the to do list.
(I'm sure you realize Y can be any main key or combination of keys.)
�Author of HotkeyNet and Mojo
Olyipcs suggestion works fine, but as i said, the workaround i used was to simply keymap each shifted combination hotkey and that's been fine. Using another key such as "y" doesn't really work for my key layout.
Connect With Us