Using clicks and not hotKeys to control the "enslave"?

Quote:

---

Originally Posted by 'flep',index.php?page=Thread&postID=72585#post7258 5

For example, with the HotkeyNet i can send a "mouse click" for the background wow, using a keybind [got the example on the site and works fine]. If this can be done simple with the MouseClick as a hotkey, sending the exactly mouseclick for the background wow, i can just create a fake buttons on my wow1 and put the functions on the same X,Y on the wow2, so, when i click on my wow1 fake bar, will duplicate the click on the wow2.

---

Sorry I forgot to answer this. Yes you can do this now with HotkeyNet. I added mouse triggers to HotkeyNet in build 103 a couple of days ago. If you put the windows on the same X,Y you should also write "NoMove" in <MouseClick> to make the execution very fast. Or you can put the windows on different X,Y's and HKN will move and scale the cursor position, but that adds a little bit of latency. You can also send the click to only the background window if you want even though you're clicking on the top one.

Quote:

---

Originally Posted by 'Freddie',index.php?page=Thread&postID=72592#post7 2592

Quote:

---

Originally Posted by 'flep',index.php?page=Thread&postID=72585#post7258 5

For example, with the HotkeyNet i can send a "mouse click" for the background wow, using a keybind [got the example on the site and works fine]. If this can be done simple with the MouseClick as a hotkey, sending the exactly mouseclick for the background wow, i can just create a fake buttons on my wow1 and put the functions on the same X,Y on the wow2, so, when i click on my wow1 fake bar, will duplicate the click on the wow2.

---

Sorry I forgot to answer this. Yes you can do this now with HotkeyNet. I added mouse triggers to HotkeyNet in build 103 a couple of days ago. If you put the windows on the same X,Y you should also write "NoMove" in <MouseClick> to make the execution very fast. Or you can put the windows on different X,Y's and HKN will move and scale the cursor position, but that adds a little bit of latency. You can also send the click to only the background window if you want even though you're clicking on the top one.

---

Really?? Can you put an example of the mouseclick1? I have the 103 build but dont know how to put the mouse click on the script.

Ty

Sure. The button names changed in build 104. I'll use the new names from 104 in these examples.

To start off, here's a hotkey that does what you described. Your two WoW's are the same size, at the same location. You press the left button and both windows get clicked.

Code:

---

<Hotkey LButton>
<SendWinM wow1>
<MouseClick NoMove LButton>
<SendWinM wow2>
<MouseClick NoMove LButton>

---

Like I said earlier, you don't need to have the windows in the same place. They don't even have to be the same size. If you move them or resize them, take "NoMove" out of the second <MouseClick> like this:

Code:

---

<Hotkey LButton>
<SendWinM wow1>
<MouseClick NoMove LButton>
<SendWinM wow2>
<MouseClick LButton>

---

Those hotkeys work okay but they might be annoying because they *always* click both windows when you press the mouse button. It might be better to make a hotkey that does that only sometimes. Here's one way to do that. Pick a key on your keyboard that's easy to find, but doesn't get used much. On US-English keyboards, the Grave key (upper left corner) is a good choice. Declare that as a custom modifier (a shift key). Then define the hotkey so it gets triggered only when Grave is held down simultaneously with the left button. The result looks like this:

Code:

---

<UseKeyAsModifier Grave>
<Hotkey LButton>
<SendWinM wow1>
<MouseClick LButton>
<SendWinM wow2>
<MouseClick LButton>

---

And that leads up to Katharsis's example from this other thread:

HotkeyNet + AOE!