or [HotKeyNet] functionality

[olipcs]

the <if>,<Else If>,<else> can have as many <elseif>s as you like, but you can'T nest <if>s inside of <if>s.

[wolpak]

Ok, if this works, I'll post about it here. Sorry for thinking you didn't have this functionality, but it looks like it works how I envisioned it...to a degree.

[Freddie]

Sorry for thinking you didn't have this functionality...

Absolutely not your fault! The program has dozens or even hundreds of features that hardly anyone knows about. That's the problem with a script-driven program. The features are invisible unless you plow through the documentation. Hardly anyone is going to spend hours reading all that stuff.

How many nested If statements can we have? I mean, that is going to be one long Hot key if I have 2 slaves and want to map like 12 buttons each.

Sure it will be long but you have to write a definition for each button somewhere, so why not in a hotkey definition? It's just syntax. Like Olipcs said there's no length limit.

[wolpak]

I am going to see if I can find any script that will output the cordinates of my mouse on a press since I have no idea what they are onscreen. Unless you want to tell me first.

[Freddie]

HotkeyNet shows you the coordinates in its upper right window each time you click .... but only if you've loaded a script that has at least one hotkey with a mouse button in its trigger.

It does this for efficiency reasons -- it only loads a mouse hook when absolutely necessary, to avoid slowing your PC even a tiny bit.

You can load this hotkey if you need to:

<Hotkey LCtrl RAlt RButton>
<ToggleWin X Y>

That will never get triggered (unless you have three hands, because that's how many you need to press that combination of buttons), but it will cause HotkeyNet to load a mouse driver.

[wolpak]

Trying to figure this out. Not sure what coordinates the parameters are looking for, the window or the screen. Either way, it seems like it has hijacked my mouse to not do anything at all if the conditions are not met.

[Freddie]

Not sure what coordinates the parameters are looking for, the window or the screen.

If you write <If MouseIsOverWindowRect ...> like we showed you, it uses window coordinates. If you want to use screen coordinates, you would write <If MouseIsOverScreenRect ...>.

Either way, it seems like it has hijacked my mouse to not do anything at all if the conditions are not met.

That's why Olipcs corrected my example. You need to add a final "Else" for that case. But I just tested and here's the best way to write it. This should go at the end:

<Else>
   <SendFocusWin>
      <ClickMouse NoMove %Trigger%>

[wolpak]

I am not sure that the coordinates are being populated properly. It might have something to do with the focus window though. However, it highjacks the mouse on all left clicks. I cannot left click any other screen or even anything on my screen. For some reason it triggers for everything.

[wolpak]

Also, is there a way to bracket in the individual keys. I have no idea what the program is looking for in terms of completed functions.



<Hotkey Home>
<SendLabel warlock>
<Keydown up>

When it reads the first line, is it looking for two more lines? One a SendLabel and the other a Key stroke?

[Freddie]

I am not sure that the coordinates are being populated properly.

It would generate error messages if that were the case.

However, it highjacks the mouse on all left clicks.

To reduce your frustration level, I very strongly recommend that you test this with some other trigger until you get it working. I would test with this trigger:

<Hotkey Shift RButton>

That way your test hotkey won't get triggered unless you hold down a shift key and press right button.