Greatwind
12-18-2012, 03:06 PM
Hello,
I'm using the following code, the sample from HotKeyNet modified to my needs.
// SUBROUTINE TO LAUNCH AND RENAME A COPY OF WOW. -------------------
<Command LaunchAndRename>
<SendPC %1%>
<Run %2%>
<RenameTargetWin %3%>
<RemoveWinFrame>
<SetAffinity %4%>
// HOTKEY TO LAUNCH AND RENAME YOUR WOW WINDOWS while 2 boxing -------------------
<Hotkey Alt Ctrl L>
<LaunchAndRename Local "C:\Program Files (x86)\World of Warcraft\Wow-64.exe" WoW1 1>
<LaunchAndRename Local "C:\Program Files (x86)\World of Warcraft\Wow-64.exe" WoW2 2>
<Hotkey Alt Ctrl D>
<SendPC Local>
<ToggleHotKeys>
// DEFINE MAIL LABELS FOR SENDING KEY STROKES. ------------------
<Label w1 Local SendWinM WoW1>
<Label w2 Local SendWinM WoW2>
// DEFINE HOTKEYS FOR ALL KEY COMBINATIONS THAT WILL GET -----------------------
// SENT TO ALL WOWS. ADD MORE KEY COMBO'S IF YOU WANT. ---------------------
<KeyList MyList r, g, c, x, q, e, t, y, 0-9, NUMPAD0 - NUMPAD9, Oem3, Oem4, Space, NUMPAD0 - NUMPAD9, NumpadPlus, NumpadMinus>
<Hotkey MyList; Shift MyList; Ctrl MyList; Alt MyList>
<SendLabel w2, w1>
<Key %TriggerMainKey%>
<MovementHotkey left, right, up, down>
<SendLabel w1>
<Key %Trigger%>
<KeyList MouseList MButton, Button4>
<Hotkey MouseList; Shift MouseList; Alt MouseList; Ctrl MouseList>
<SendLabel w1, w2>
<ClickMouse %TriggerMainKey%>
<Key Button5>
<Hotkey Shift Button5; Alt Button5; Ctrl Button5>
<SendLabel w1, w2>
<ClickMouse %TriggerMainKey%>
I do not get any errors upon loading the script except for the AutoExec one.
When a Numpad button is clicked either on the keyboard or G600 mouse, it only works in the active window. There's no error messages, the log says the keystroke was sent to both windows successfully. Like this:
From this pc: <SendWinM WoW2><Key NUMPAD5><SendWinM WoW1><Key NUMPAD5>
<SendWinM WoW2> completed: Window found. Target set to 0x1E0122 "WoW2"
<Key NUMPAD5> completed
<SendWinM WoW1> completed: Window found. Target set to 0x2301F8 "WoW1"
<Key NUMPAD5> completed
The mouse ones do give me the "specified Window is minimized" or something like that for the second window, but here is the thing - I recall all of those working a day ago or so. Then, after messing with the script, changing things around, and then changing it back to how it was, it doesn't work anymore. I don't believe the WoW clients were in Windowed mode back then, but I could be wrong.
The question is, is Windowed mode required for both clients to broadcast all the clicks? If the regular ones like letters, digits, space, Tab, F keys broadcast to both windows in Fullscreen, with one of them minimized, how come the Numpad ones don't? The mouse ones aren't even that important, so if those are impossible in Fullscreen, then it's w/e.
I'm using the following code, the sample from HotKeyNet modified to my needs.
// SUBROUTINE TO LAUNCH AND RENAME A COPY OF WOW. -------------------
<Command LaunchAndRename>
<SendPC %1%>
<Run %2%>
<RenameTargetWin %3%>
<RemoveWinFrame>
<SetAffinity %4%>
// HOTKEY TO LAUNCH AND RENAME YOUR WOW WINDOWS while 2 boxing -------------------
<Hotkey Alt Ctrl L>
<LaunchAndRename Local "C:\Program Files (x86)\World of Warcraft\Wow-64.exe" WoW1 1>
<LaunchAndRename Local "C:\Program Files (x86)\World of Warcraft\Wow-64.exe" WoW2 2>
<Hotkey Alt Ctrl D>
<SendPC Local>
<ToggleHotKeys>
// DEFINE MAIL LABELS FOR SENDING KEY STROKES. ------------------
<Label w1 Local SendWinM WoW1>
<Label w2 Local SendWinM WoW2>
// DEFINE HOTKEYS FOR ALL KEY COMBINATIONS THAT WILL GET -----------------------
// SENT TO ALL WOWS. ADD MORE KEY COMBO'S IF YOU WANT. ---------------------
<KeyList MyList r, g, c, x, q, e, t, y, 0-9, NUMPAD0 - NUMPAD9, Oem3, Oem4, Space, NUMPAD0 - NUMPAD9, NumpadPlus, NumpadMinus>
<Hotkey MyList; Shift MyList; Ctrl MyList; Alt MyList>
<SendLabel w2, w1>
<Key %TriggerMainKey%>
<MovementHotkey left, right, up, down>
<SendLabel w1>
<Key %Trigger%>
<KeyList MouseList MButton, Button4>
<Hotkey MouseList; Shift MouseList; Alt MouseList; Ctrl MouseList>
<SendLabel w1, w2>
<ClickMouse %TriggerMainKey%>
<Key Button5>
<Hotkey Shift Button5; Alt Button5; Ctrl Button5>
<SendLabel w1, w2>
<ClickMouse %TriggerMainKey%>
I do not get any errors upon loading the script except for the AutoExec one.
When a Numpad button is clicked either on the keyboard or G600 mouse, it only works in the active window. There's no error messages, the log says the keystroke was sent to both windows successfully. Like this:
From this pc: <SendWinM WoW2><Key NUMPAD5><SendWinM WoW1><Key NUMPAD5>
<SendWinM WoW2> completed: Window found. Target set to 0x1E0122 "WoW2"
<Key NUMPAD5> completed
<SendWinM WoW1> completed: Window found. Target set to 0x2301F8 "WoW1"
<Key NUMPAD5> completed
The mouse ones do give me the "specified Window is minimized" or something like that for the second window, but here is the thing - I recall all of those working a day ago or so. Then, after messing with the script, changing things around, and then changing it back to how it was, it doesn't work anymore. I don't believe the WoW clients were in Windowed mode back then, but I could be wrong.
The question is, is Windowed mode required for both clients to broadcast all the clicks? If the regular ones like letters, digits, space, Tab, F keys broadcast to both windows in Fullscreen, with one of them minimized, how come the Numpad ones don't? The mouse ones aren't even that important, so if those are impossible in Fullscreen, then it's w/e.