
Originally Posted by
dubiox
Well I really tried to be clear but I failed. As written, you can't click and drag _outside the region_ when ScrollLock is on (or if I remove the modifier). So you can't move the camera or drive with both buttons. I would like to have normal mouse usage outside the region and not have to use a modifier at all inside the region. Sounds like that is not possible.
This is because you've turned your left mouse button into a hotkey, removing its ability to act like a mouse key. You would need to redefine the entire function of the button to do what you're trying to do -
Code:
<Hotkey LButton>
<If MouseIsOverScreenRect 1980 1250 495 120>
<SendLabel w1, w2, w3, w4, w5>
<ClickMouse LButton>
<Else>
<SendFocusWin>
<ClickMouse LButton Down NoMove NoRestore>
<HotkeyUp LButton>
<SendFocusWin>
<ClickMouse LButton Up NoMove NoRestore>
I guess I can do something like control-shift-click which is less hassle than hitting scrolllock then clicking.
I would really advise against passing mouse clicks. Every time you pass the mouse you chance lagging your system as each window takes focus. This can leave your mouse "trapped" on a slave window and can cause a lot of head aches. It also requires that the UIs be exact in order for the mouseclick to land properly and that you not spam the key so it's not picking up coordinates off a slave window halfway through the pass cycle, which can also make the mouse Return to a slave window instead of the main window. Then you manually need to click the main window again to make it active.
This is why it is advised that new multiboxers learn how to press Hotkeys instead of clicking the hotbars for DPS, no matter the multiboxing software. It's great for things like AOE or portal useage where it doesn't need to be exceedingly accurate or fast but sending keys is always the most efficient option since every window can receive the command at once rather than having to wait their turn/squabble over the limited resource of a single cursor.
If you still want to use mouse passing, then skip the region and just use a toggle or modifier for universal mouse passing like the default OEM3 in the starter scripts {removing the ScrollLockOn} -
Code:
//-----------------------------------------------------------
// BROADCAST MOUSE CLICKS. HOLD DOWN OEM3 (ON U.S. KEYBOARDS,
// THAT'S THE SQUIGGLE KEY IN UPPPER LEFT CORNER) WHEN YOU
// WANT TO BROADCAST.
//-----------------------------------------------------------
<UseKeyAsModifier Oem3>
<Hotkey Oem3 LButton, MButton, RButton, Button4, Button5>
<SendLabel w1, w2>
<ClickMouse %TriggerMainKey%>
Well sure that would be great but I can't come up with and remember 20 more hotkeys.
1 - you don't have to remember 20 keys, that's the entire point of the region definitions. The key sent changes based on your mouse's position in the region.
2 - WoW can take any combination of the standard modifiers CTRL/ALT/Shift, which means you can have 1, Ctrl 1, Alt 1, Shift 1, Ctrl Alt 1, Ctrl Shift 1, Alt Shift 1 and Ctrl Alt Shift 1. WoW can also distinguish between left and right modifiers in macros, so you can have a single macro that covers multiple button modifiers just like an FTL Macro
Code:
/click [mod:lalt] JambaItemUseContainerButton1; [mod:ralt] JambaItemUseContainerButton2; [mod:lctrl] JambaItemUseContainerButton3; [mod:rctrl] JambaItemUseContainerButton4; [mod:lshift] JambaItemUseContainerButton5; [mod:rshift] JambaItemUseContainerButton5; [mod:lalt lctrl] JambaItemUseContainerButton6; [mod:ralt rctrl] JambaItemUseContainerButton7; [mod:lalt lshift] JambaItemUseContainerButton8; [mod:ralt rshift] JambaItemUseContainerButton9; [mod:lctrl lshift] JambaItemUseContainerButton10; [mod:rctrl rshift] JambaItemUseContainerButton11; ETC
You would then simply configure the HotKeyNet code to send those modified keys to that macro in WoW, so rather than HKN sending Ctrl Numpad1, Ctrl Numpad2 etc, it is sending 1, LAlt 1, RAlt 1, LShift 1, LCtrl LShift 1.... based on the region your mouse is over. Nothing changes about the key you physically press no matter if you are triggering ItemBar1 or ItemBar20.
3 - I have never needed more than 6 Item Bar slots at any given time. I've got them all keybound, but I've never needed to use anything above ItemBar6 and only have 4 slots actually showing.
Connect With Us