It jumps to the other window because that's the only place you told it to go with <sendwin WoW2>. That's not how you structure hotkeys.
First, this hotkey {1} should already be defined in the standard script under the keylist. You shouldn't need to redefine it as an individual hotkey.
If you're using the sample script from here, 1 is already defined as a hotkey in these lines {highlighted in red} :
Code:
//-----------------------------------------------------------
// DEFINE HOTKEYS FOR ALL KEY COMBINATIONS THAT WILL GET
// SENT TO BOTH WOWS. ADD MORE KEY COMBO'S IF YOU WANT.
//-----------------------------------------------------------
<Hotkey ScrollLockOn A-Z, 0-9, Plus, Minus, F1-F12 except W, A, S, D, Q, E>
<SendLabel w1, w2>
<Key %Trigger%>
As far as the command you've written for Hotkey 1, you have a couple problems.
The sample script uses SendWinM, you should avoid using differing sendmodes in your script.
You shouldn't define sendmodes in hotkeys. Hotkeys should use the Label that is defined at the start of the script, in the "Mail Labels" section -
Code:
//-----------------------------------------------------------
// DEFINE MAIL LABELS FOR SENDING KEY STROKES
//-----------------------------------------------------------
<Label w1 Local SendWinM WoW1>
<Label w2 Local SendWinM WoW2>
These mail labels also already define that the PC is Local, there's no need to define it again in the hotkey itself.
Finally, under normal circumstances, your script should be throwing errors about 1 already being defined, but the sample script is set up with a modifier for the keylist
Code:
// Toggle the scroll lock key to turn hotkeys off and on. (You
// can change this if you want, just like you can change
// everything else with HotkeyNet.)
Code:
//-----------------------------------------------------------
// DEFINE HOTKEYS FOR ALL KEY COMBINATIONS THAT WILL GET
// SENT TO BOTH WOWS. ADD MORE KEY COMBO'S IF YOU WANT.
//-----------------------------------------------------------
<Hotkey ScrollLockOn A-Z, 0-9, Plus, Minus, F1-F12 except W, A, S, D, Q, E>
<SendLabel w1, w2>
<Key %Trigger%>
HotKeyNet's sample script is set up so that if you do not have scroll lock ON, you are not broadcasting keys. This way when Scroll Lock is off, you can run your active window without sending anything to your slave window. Adding the additional hotkey without the Scroll Lock On modifier means that 1 will be sent all the time.
A properly constructed hotkey, assuming it wasn't defined in the keylist, should look like this
Code:
<Hotkey ScrollLockOn 1>
<SendLabel w1, w2>
<Key 1>
The link in my sig for HotKeyNet breaks down every line of the starter script and explains how to use and modify it.
Connect With Us