HotKeyNet how to use it?

[dRiN]

I have two pc's and 2 laptops. On one of the laptops I'm running two wow clients.

What I would like to do with HotKeyNet is passing through some keys to 4 instances of WoW and keep all keys falling through on my server pc.

To rename the two wow windows on a remote pc I use the next script. [code:1]
// renames wow windows on laptoprin
<hotkey ctrl R>
<sendpc xxx.xxx.xxx.xxx>
<rename "World of Warcraft" wow1>
<rename "World of Warcraft" wow2>
[/code:1]

Next I use to make sure the 1 key falls through to both wow's running on the laptop and that the 1 key works on the server.
[code:1]
<hotkey 1>
<sendpc local>
1
<sendpc 172.19.3.3>
<sendwin wow1>
1
<sendwin wow2>
1
[/code:1]

This does not work. I will get an error for the key that is sent to my local machine. Can I only make this work when I insert a named window? And I cannot use the keys outside the running wow instance?

WSASend() error
[OK]

When I use the following code
[code:1]
<hotkey 1>
<sendpc local>
<sendwin "World of Warcraft">
1
<sendpc 172.19.3.3>
<sendwin wow1>
1
<sendwin wow2>
1
[/code:1]

There is still the error for WSASend() error.

What am I doing wrong?

Another question. Can I bind a key to temporarily shutdown the keysending?

[Freddie]

Sorry to hear you're having trouble. Let's try to simplify the problem to help us figure out the cause. These three lines work on my PC:

[code:1]
<hotkey 1>
<sendpc local>
1[/code:1]

Could you try simplifying the hotkey definition to the three lines shown here, and see if the WSASend error pops up at the precise moment when you trigger this hotkey?

> Can I only make this work when I insert a named window?

You can define hotkeys without specifying a "send to" window. If you do that, output goes to whichever window has the focus (i.e. is active).

> And I cannot use the keys outside the running wow instance?

Sorry, I don't understand this question.

> Can I bind a key to temporarily shutdown the keysending?

No, but you can do that with the check box at the bottom of HotkeyNet's main panel.

[dRiN]

Thanks for the quick response.

[code:1]
<hotkey 1>
<sendpc local>
1
[/code:1]

This works perfectly, it passes through on whatever window I type.

[code:1]
<hotkey 1>
<sendpc local>
1
<sendpc 172.19.3.3>
1
[/code:1]

This does not work for me. It will send the 1 key to the 172.19.3.3 client. But it will give an error on the server and won't send the 1 key.

When loading the hotkey.txt file it gives this information in a window.
[code:1]
cHotkeyTable: 1
cHotMainKey: 1 ModStates: 1

<1>
SendTo = 0.0.0.0 "" 3896616
SendTo = 172.19.3.3 "" 0
[/code:1]

Hope you can help me out with this problem and hopefully make it better for future users also : )

[Freddie]

Let me make sure I understand what you mean by "server." I assume you mean the local machine, which is the one on which you are pressing the hotkey. Is that right?

Could you try two more definitions? Please note that I'm changing the output character to make it different from the hotkey, for diagnostic purposes. And also let's separate the outputs into separate definitions.

[code:1]<hotkey 1>
<sendpc local>
2 [/code:1]

And the second one:

[code:1]<hotkey 3>
<sendpc 172.19.3.3>
4[/code:1]

Thanks a lot.

[dRiN]

Let me make sure I understand what you mean by "server." I assume you mean the local machine, which is the one on which you are pressing the hotkey. Is that right?

This is correct.

Could you try two more definitions? Please note that I'm changing the output character to make it different from the hotkey, for diagnostic purposes. And also let's separate the outputs into separate definitions.

Tried both.

[code:1]<hotkey 1>
<sendpc local>
2 [/code:1]

This standalone in the config.txt file is working okay.

And the second one:
[code:1]<hotkey 3>
<sendpc 172.19.3.3>
4[/code:1]

This stand alone does not work. It gives the error mentioned before on the server side. It does send the 4 to the client though.

Thanks a lot.

No, thank you!

[Freddie]

> This stand alone does not work. It gives the error mentioned
> before on the server side. It does send the 4 to the client
> though.

I'm confused. The only thing that definition does is send a 4 to 172.19.3.3. If that is happening, then the hotkey is working.

Maybe we're having a communications problem. Let me make sure of a few things:

1. You're loading this file on only one machine.

2. That machine does not have the IP address 172.19.3.3.

3. From now on I'm going to call that machine (which is not 172.19.3.3) the "local" pc. (It's irrelevant whether it's the client or server. You can forget about clients and servers when you define and use hotkeys.)

4. You are pressing "3" on the local machine, and "4" is output on 172.19.3.3.

If any of that is wrong, please tell me so I can understand the problem better.

[dRiN]

> This stand alone does not work. It gives the error mentioned
> before on the server side. It does send the 4 to the client
> though.

I'm confused. The only thing that definition does is send a 4 to 172.19.3.3. If that is happening, then the hotkey is working.

This is happening, but I do get an error with a popup. If the error was silent it was no problem at all.

Maybe we're having a communications problem. Let me make sure of a few things:

1. You're loading this file on only one machine.

I am loading it on 172.19.3.10 only.

2. That machine does not have the IP address 172.19.3.3.

Correct.

3. From now on I'm going to call that machine (which is not 172.19.3.3) the "local" pc. (It's irrelevant whether it's the client or server. You can forget about clients and servers when you define and use hotkeys.)

Okay.

4. You are pressing "3" on the local machine, and "4" is output on 172.19.3.3.

Correct.

If any of that is wrong, please tell me so I can understand the problem better.

Desktop 172.19.3.10 loaded config on it. With the params you gave. Pressed 3, and 4 popped up on 172.19.3.3. Only problem is that on 172.19.3.10 I still get an [OK] error box.
[code:1]
WSASend() error
[OK]
[/code:1]

[Freddie]

Thanks for explaining this so patiently.

I understand the problem now but I can't reproduce it here so I need to ask you to help me pinpoint the cause.

If you don't mind, I'd like to ask you to please download the new build (34) of the program that I just put on the website. This new build will (hopefully) display a different error message with more info when you run that macro.

Also, a question. Which versions of Windows are running on the two machines?

[dRiN]

Thanks for explaining this so patiently.

I understand the problem now but I can't reproduce it here so I need to ask you to help me pinpoint the cause.

If you don't mind, I'd like to ask you to please download the new build (34) of the program that I just put on the website. This new build will (hopefully) display a different error message with more info when you run that macro.

Also, a question. Which versions of Windows are running on the two machines?

Im only running XP. Will try the new version when I get home later today and post back the results later. Is it maybe possible to not put the error messge in an ok box, but maybe in a log file in the folder where the program is running?

[Freddie]

I'd like to figure out what's causing the error message. If there is really a problem, I'll fix it. If there isn't a real problem, I'll remove the error message entirely.