Elzam
12-14-2014, 09:16 PM
Edit: Modifying my hotkeys and changing them back oddly seems to have worked. Mods please delete thread if you feel it appropriate. SOLVED.
So I'm new to dual-boxing and I'm running the default 2on1 setup. It's worked quite decently for what I'm doing thus far.
However, I suddenly had a crash on my Master unit (WoW1) while the Slave (WoW2) stayed online. Upon logging back in and since, when I have my Hotkeys active through Scroll Lock, hotkeys send signals to WoW2 while WoW1 acts like nothing has been pushed. The buttons can be clicked, of course, but that doesn't trigger the HKN hotkey. :P
Buttons which do not have associated Hotkeys assigned across the two windows function normally. The HotKeyNet window appears to be giving a successful message:
From this pc: <SendWinM WoW1><Key 1><SendWinM WoW2><Key 1>
<SendWinM WoW1> completed: Window found. Target set to 0x202A8 "WoW1"
<Key 1> completed
<SendWinM WoW2> completed: Window found. Target set to 0x2025A "WoW2"
<Key 1> completed
In short, whichever window is the active one is not receiving the key presses. This problem persists despite reloading script, restarting PC, and ensuring the script is correct by complete deletion and recreation.
So I'm new to dual-boxing and I'm running the default 2on1 setup. It's worked quite decently for what I'm doing thus far.
However, I suddenly had a crash on my Master unit (WoW1) while the Slave (WoW2) stayed online. Upon logging back in and since, when I have my Hotkeys active through Scroll Lock, hotkeys send signals to WoW2 while WoW1 acts like nothing has been pushed. The buttons can be clicked, of course, but that doesn't trigger the HKN hotkey. :P
Buttons which do not have associated Hotkeys assigned across the two windows function normally. The HotKeyNet window appears to be giving a successful message:
From this pc: <SendWinM WoW1><Key 1><SendWinM WoW2><Key 1>
<SendWinM WoW1> completed: Window found. Target set to 0x202A8 "WoW1"
<Key 1> completed
<SendWinM WoW2> completed: Window found. Target set to 0x2025A "WoW2"
<Key 1> completed
In short, whichever window is the active one is not receiving the key presses. This problem persists despite reloading script, restarting PC, and ensuring the script is correct by complete deletion and recreation.