Could you try changing SendWinM to SendWinS, and make sure "Use new SendWinS and SendWinSF" is checked on Send Mode Settings.
Could you try changing SendWinM to SendWinS, and make sure "Use new SendWinS and SendWinSF" is checked on Send Mode Settings.
�Author of HotkeyNet and Mojo
You're welcome.
That's the program's default behavior. If you want to change that, uncheck "Clear modifiers before executing hotkey" on Settings.
There's also a way to adjust that behavior for individual hotkeys, if you need to do that.
�Author of HotkeyNet and Mojo
Could you please post the entire script exactly as you're loading it.
Last edited by Freddie : 09-04-2009 at 11:35 AM
�Author of HotkeyNet and Mojo
This is the script I am using
I did the mYkeys2 list for testing.Code:<Hotkey Alt Ctrl L> <if WinDoesNotExist wow1> <RenameWin "World of Warcraft" wow1> <else> <RenameWin "World of Warcraft" wow2> <Label w1 Local SendWinS wow1> <Label w2 Local SendWinS wow2> <KeyList mYkeys A-Z, 0-9, F1-F12, except w,a,s,d> <KeyList mYkeys2 2> <Hotkey mYkeys2; alt mYkeys2; ctrl mYkeys2> <SendPC local> <SendLabel w1, w2> <Key %TRIGGER%>
I just tested this. You found a problem with the way SendWinS handles "clear modifiers." Thanks for reporting it. I'll try to fix it later today.
I also just tested the original problem you reported and I can't reproduce it. This works properly for me with the old SendWinM. Are you running any other software that modifies the keyboard in any way?
By the way, when you describe these problems to me, it would be extremely helpful if you would tell me:
1. Which hotkey is getting triggered. (You can see this in HotkeyNet's upper left window.)
2. Whether HotkeyNet says it's sending the modifier (you can see this in HotkeyNet's main window).
3. Whether WoW receives the modifier.
Those are three different things. Thanks.
�Author of HotkeyNet and Mojo
Connect With Us