HotKeyNet how to use it?

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?

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.

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 : )

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.

Quote:

---

Originally Posted by 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?

---

This is correct.

Quote:

---

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.

Quote:

---

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

---

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

Quote:

---

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.

Quote:

---

Thanks a lot.

---

No, thank you!

> 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.

Quote:

---

Originally Posted by 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.

---

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

Quote:

---

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.

Quote:

---

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

---

Correct.

Quote:

---

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.

Quote:

---

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

---

Correct.

Quote:

---

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]

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?

Quote:

---

Originally Posted by 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?

---

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?

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.

Configuration
main : 172.19.3.10 (XP)
other : 172.19.3.3 (XP)

Code:

---

<hotkey 3>
<sendpc 172.19.3.3>
4

---

Gives the following error.

WSASend() error; retval = -1, error = 997

Great. That error code explains what was happening. It indicates a normal condition rather than an error. My program was reacting to the normal condition as if it was an error and putting an unnecessary error message on your screen.

I just removed the error message and put a new build of the program (number 35) on the website. Hopefully this will fix the problem for you.

Thank you very much for your patience and your help in getting this problem solved. I know it's frustrating, and I really appreciate it.

Thanks for the new version. It is working as intended : )

Now for another question. I have two windows on my laptop that I rename from a hotkey from the main. Those wow's are stared from two seperated locations. c:\...\wow1 and c:\...\wow2. Is there a way to make sure that it always names the one started from wow1 to wow1? And the one started from wow2 to wow2? In what way can I control this?

Glad to know we fixed it. :)

The easiest way to handle your new question is to click on the "first WoW" just before you press the hotkey.

If you want the nitty-gritty details, here's how the order of renaming is determined with XP:

-- If only one WoW is non-minimized, it gets renamed first.

-- If both WoWs are non-minimized, the one that is on top of the other gets renamed first.

-- If both WoWs are minimized, the one to the left on the taskbar gets renamed first.

Or you can avoid this whole issue by using two separate hotkeys, one for each WoW.

If you can think of a better way to handle this, I'll add it to the program.

[quote='dRiN',index.php?page=Thread&postID=28970#po st28970]Now for another question. I have two windows on my laptop that I rename from a hotkey from the main. Those wow's are stared from two seperated locations. c:\...\wow1 and c:\...\wow2. Is there a way to make sure that it always names the one started from wow1 to wow1? And the one started from wow2 to wow2? In what way can I control this?[/quote]

I thought some more about your question and decided to add a new command so you can rename windows based on the folder of the program file. The syntax is:

[color=#0000ff][font='Courier New, Courier, mono']<rename_from_path path name>[/font][/color]

Here's an example:

Code:

---

<hotkey ctrl R>
    <sendpc local>
        <rename_from_path "c:\Program files\wow1\" Name1>
        <rename_from_path "c:\Program files\wow2\" Name2>

---

You can specify either the whole path including the executable file name or just the directory, whichever you prefer. I used quotes in the example because the paths have spaces in them.

I just downloaded version 58 and am having probles with it. I am running it on 2 machines, a pc and a laptop. both run Vista. the laptop runs 64 bit vista. I set the local/server machine on the PC, and the remote/client on the laptop. I am using it to play World of Warcraft. I created a hotkey file that basically transmits the numbers 1-0 plus teh - and the = to the remote when I press the corresponding numbpad key (which I do not use for the game on the local machine, that way I can send commands without affecting what I am doing on the local machine). this in return activates the corresponding hotkey on my action bar on the laptop/remote system. the two systems connect fine. the remote system receives the command I send it fine.

Problem #1 is that when I went to setup the window name for the commands to be sent to I changed it to "wow" to make the code shorter. well I later noticed that when using the change the name of the window pop-up, that every window on my system was now called "wow" (ie. I had the World of Warcraft directory open in explorer, when I have the change window name pop-up open an dhover over the explore tab on the task bar, it tells me the windows current name is "wow", I also had an ie window open, and Hotkeynet tells me that windows name is "wow".

So, I tried to test this. on my local/server PC I opened the window rename pop-up, and moused over several windows. in the hotkeynet change window name pop-up EVERY tab for ALL my programs was called "Application". So, I believe this to be an issue with Vista and hotkeynet not pulling the correct information (I am assuming from the registry). AND causes any renames to a have a global effect on every open window (even if you close the window and rename it). as a result I would like to have a new setting in the program that allows you to add/remove renaming from specific files/folders/applications.

I also tried getting around this by renaming a specific program by location window (which you ned to update the command for this on the website. on the website it has "_" between every word, when I tried this hotkeynet told me I no longer need "_" between words, and the words were justputtogether <--- example. This did nothing, as the site did not tell me if I had to attach this to a hotkey and send it to the remote machine from the local, or enter it at the command prompt, or how to do it.



Problem #2 is, after I press a hotkey locally, the remote system responds correctly. the SECOND hotkey I press usually does nothing, even if it is the same hotkey I just used. SOMETIMES I can press up to 5 or 6 hotkeys and it will do nothing, SOMETIMES I can only pre3ss the second hotkey and it will do nothing, THEN The remote system will "alt-tab" itself to the desktop, as the desktop is now considered a "active window" in Vista. I am assuming this is the "bring to forground" issue mentioned on the website, so I tried <sendwinM wow> same result. I would like to think this problem is a result of Problem #1. I also tried using the <foreground wow> command, and this had no result. I also tried using the <restore> command, this had no result. I tried using these commands before and/or after the command being issued.

I have tried changing the window name as well, and nothing is different.

here is the hotkey.txt file I am using.

<hotkey numpad1>
<sendpc 192.168.2.2>
<sendwin World of Warcraft>
1
<hotkey numpad2>
<sendpc 192.168.2.2>
<sendwin World of Warcraft>
2
<hotkey numpad3>
<sendpc 192.168.2.2>
<sendwin World of Warcraft>
3
<hotkey numpad4>
<sendpc 192.168.2.2>
<foreground wow>
<sendwin wow>
4
<restore>
<hotkey numpad5>
<sendpc 192.168.2.2>
<sendwin wow>
5
<restore>
<hotkey numpad6>
<sendpc 192.168.2.2>
<sendwin wow>
6
<hotkey numpad7>
<sendpc 192.168.2.2>
<sendwin wow>
7
<hotkey numpad8>
<sendpc 192.168.2.2>
<sendwin wow>
8
<hotkey numpad9>
<sendpc 192.168.2.2>
<sendwin wow>
9
<hotkey numpad0>
<sendpc 192.168.2.2>
<sendwin wow>
0
<hotkey numpad_minus>
<sendpc 192.168.2.2>
<sendwin wow>
-
<hotkey numpad_plus>
<sendpc 192.168.2.2>
<sendwin wow>
=
<hotkey numpad_enter>
<sendpc 192.168.2.2>
<RenameFromPath "c:\Program Files (x86)\World of Warcraft\Wow.exe" wow>
<sendpc 192.168.2.2>
<RenameFromPath "c:\Program Files (x86)\World of Warcraft\Launcher.exe" wow>

Finndo, thanks very much for the report. I'll address your specific points in a moment but first let me say, you have two rename commands for the same PC for the hotkey that's triggered by <Numpad_Enter>. I don't know if you are trying to rename two different windows or whether you did this because you weren't sure which pathname to use, but either way, you need to change this. If you are trying to rename two different windows on the same PC, you have to give them different names like this:

<Rename "World of Warcraft" wow1>
<Rename "World of Warcraft" wow2>

If you have only one WoW window on that machine, you don't need to bother renaming it. You can refer to it as "World" in your files. HKN matches the first window that begins with "World."

If you have only one WoW window on that machine, and for some reason you want to rename it anyway, you have to do it like this:

<Rename "World of Warcraft" wow>

Quote:

---

Originally Posted by finndo',index.php?page=Thread&postID=38236#post382 36]Problem #1 is that when I went to setup the window name for the commands to be sent to I changed it to "wow" to make the code shorter...[/quote]If that's the only reason you're doing it, you don't need to bother. You can specify part of a window name in your definitions, and HKN will match the first window that begins that way. For example, <sendwin World> will match "World of Warcraft."

[quote='finndo

well I later noticed that when using the change the name of the window pop-up, that every window on my system was now called "wow"

---

What exactly did you right click when you selected the window to be renamed? Did you right-click the title bar at the top of the actual WoW window? (That's what I intended users to do. ) Or did you right-click something else?

Quote:

---

So, I believe this to be an issue with Vista and hotkeynet not pulling the correct information (I am assuming from the registry).

---

HKN doesn't do anything with the registry. It just looks at open windows and picks the first one, if any, that matches what you wrote. If there's no match it doesn't do anything. The changes disappear when you close the window. They aren't recorded in any way.

Quote:

---

as a result I would like to have a new setting in the program that allows you to add/remove renaming from specific files/folders/applications.

---

I think the best way to handle this is to figure out exactly what you did with the rename button, and then put in a safeguard so that can't happen. Once that is prevented, HKN only has the ability to rename specific open windows, and the user can always rename them back with the rename button or by closing the window and reopening it.

Quote:

---

I also tried getting around this by renaming a specific program by location window (which you ned to update the command for this on the website. on the website it has "_" between every word, when I tried this hotkeynet told me I no longer need "_" between words...

---

Thanks for catching the out-of-date instructions. I just changed them.

The way to get around this problem is with the <rename> command. WoW doesn't alllow itself to be renamed with <RenameFromPath> . I wasn't aware of that until i tested it a minute ago. However <Rename> works fine.

Quote:

---

Problem #2 is, after I press a hotkey locally, the remote system responds correctly. the SECOND hotkey I press usually does nothing, even if it is the same hotkey I just used.

---

I think this may be caused by the fact that you apparently have more than one window with the same name on that machine. I suggest you get the renaming fixed so there is only one window with the targeted name, and then see what happens. Let me know.

Thanks again for the report.

I was right clicking on the task bar to select the window to be renamed, as I did not have the game running in windowed mode at the time. as for trying to not rename the window, I won't be able to get to that until Friday night (next time I will be in the same place as two systems I can try it on).

Thank you for the heads up on the way the program looks for the window, I think that will help a lot. I will take the renaming out completely and let you know if I have any further issues. Once I have everything running, I am planning on running 2 instances of WoW on the same machine (the client/remote machine) and then actually playing from the other (server/local) machine. I have found that running WoW in a Virtual Machine makes the performance a little better, so I will probably have the second one (or both) running in a (separate) VM(s) (this gives it a unique IP address, in addition to avoiding the renaming issue.

I will post an update on saturday to let you know how things are going. Again thank you for responding so quickly.

okay, doing it the way you suggested fixed my problems. so I have moved on to another level... I am now connecting to client/remote machines. all went well for a few minutes... then I stopped testing and setup the interface for the 2nd remote/client machine. afterwards I was unable to receive data from the server/locel machine. I checked my hotkey.txt file and nothing had changed. I tried swapping the ip numbers in the sendpc command, and the second machine received them; however the first machine no longer received the data. here is the file I am currently using, and after is a screen shot of hotkeynet importing that same file. Pay attention to the send to IP addresses. after that is a screen shot of nslookup on those IP addresses.

<hotkey numpad1>
<sendpc 192.168.2.2><sendwin World of Warcraft>1
<sendpc 192.168.2.3><sendwin World of Warcraft>1
<hotkey numpad2>
<sendpc 192.168.2.2><sendwin World of Warcraft>2
<sendpc 192.168.2.3><sendwin World of Warcraft>2



http://www.joelperryproductions.com/.../hotkeynet.jpg


http://www.joelperryproductions.com/...s/nslookup.jpg


any ideas on this one? Like I said when I first loaded everything up, all 3 machines were working atleast a little bit, I was able to send commands to both machines, but now I can only send to one machine. If I load the hotkey.txt file I was using to run both windows on 1 remote/client machine instead of 2 remote/client machines it all works fine. here is a screen shot of an earlier attempt with this issue.



http://www.joelperryproductions.com/...ics/client.jpg



it appears that the program is having an issue determining where to end the send info and where to start looking for commands to send to another system. is there a<command> I can put in there to let the program know I am trying to connact a different system instead of forwarding on the info?

(the screen shots look horrible on my computer unless you click on them to open the full size image...)

Quote:

---

Originally Posted by 'finndo',index.php?page=Thread&postID=39363#post39 363

okay, doing it the way you suggested fixed my problems. so I have moved on to another level...

---

Good. Let's see if we can do it again with this new one.

Quote:

---

Like I said when I first loaded everything up, all 3 machines were working atleast a little bit, I was able to send commands to both machines, but now I can only send to one machine.

---

Whenever a program starts working differently like this, it's because something changed. The first step is to figure out what changed, because that's the cause of the new behavior. Once we know the cause, we know how to fix things. Luckily in this case, you probably know what changed. Because you say:

Quote:

---

all went well for a few minutes... then I stopped testing and setup the interface for the 2nd remote/client machine. afterwards I was unable to receive data from the server/locel machine.

---

You say you "setup the interface" for the second machine, and then the problem started. What exactly did you do?

Quote:

---

it appears that the program is having an issue determining where to end the send info and where to start looking for commands to send to another system.

---

The program doesn't determine this. You determine it by typing IP addresses. The program simply uses whatever IP addresses you tell it.

Here's a general explanation of how to set the IP addresses. I'm assuming here that all three machines are on the same network. If that's not the case, please let me know.

You type IP addresses in two places: (1) The clients' Communications Settings panels. (2) The hotkey files. They must be correct in both places, and you need to get the first one right before you worry about the second.

First, the Communications Settings panels. On the clients only, you need to enter the "Server's IP address. " (You don't need to enter an IP address on the server.) This is used to connect the PC's. You can tell whether the PC's are connected by looking at the bottom line on the main screens. The clients should each say they are connected to the server, and the server should say it's connected to both clients.

We know that one of your clients is connected, so we know the correct "server's IP address" is on its Communications Setting panel. But the other client may have the wrong address. If so, copy the correct address from the client that works to the one that doesn't.

If both clients have the same "server's IP address" but only one connects, and if all three machines are on the same network, then one of them is probably blocked by a firewall or router, etc.

Step two. After the three machines are connected, you need to make sure the IP addresses in your hotkey file are the same ones that are actually being used by HotkeyNet. You need to use the IP addresses that HotkeyNet is actually using, not the ones that are reported by the operating system or various utilities. The way to find the IP addresses that HotkeyNet is actually using, is by going to the Communications Setting panel on the PC that will be sending hotkeys and clicking "Show linked PC's" on the Communications Settings panel. Those are the IP addresses you need to use in your hotkey file.

After I answered Finndo today, it occurred to me that the program doesn't show the connection process very clearly to the user. This is a deficiency in the interface, and it's my fault. The process is really very simple.

1. You tell the clients the server's IP address.

2. The clients connect to the server. The program should make crystal clear whether this has happened.

3. The server asks the clients their IP addresses. These are the IP addresses that must be used in hotkey files.

So today I redesigned the program's main interface. Here's what it looks like in the new build which is not yet on the website. Before a connection takes place, the screen looks like this:

http://hotkeynet.com/art/main-screen-red-737.gif

As you can see, the screen has changed in a number of ways. But the thing I want to point out here is the big red zero at the top center. Hopefully this makes it extremely obvious to the user that the programs need to connect, but haven't done so yet.

And here's the screen after the connection takes place:

http://hotkeynet.com/art/main-screen-green-737.gif

The red has become green, so you can see at a glance that the programs have connected. In addition, I now list the IP numbers instead of the network names of the connected PCs. Why? Because these are the IP addresses that must be used in hotkey files. Hopefully now it will be obvious to users that they must use these particular IP addresses in their hotkey files.

Here's the main screen in actual use:

http://hotkeynet.com/art/main-screen-737.gif

As you can see, the program now gives much better feed back so you can see whether your definitions are written correctly. If you have any comments about the new design, please let me know. This new build will be on the website within the next few days.

appologize for not being more clear, the interface I set up was my UI in WoW (arranging the layout of the buttons, changing a few button settings, and making macros to use when the hotkeynet program issues the commands to the system.)

When I first started up hotkeynet on the 3rd computer, it connected to the server/local machine right away (after changing it to a client and restarting it) and both machines said they were connected to the same host. Afterwards I pressed a couple of hot keys to see if everything was typed in correctly in the hotkey.txt file. and I got the responses I was looking for. I then spent about 20 - 30 minutes setting up the in game UI for WoW to the way that I liked it. after this I went back to the server/local machine and started to play. after a few minutes I noticed the 3rd computer was not responding to an further commands that I sent to it, but they were working on the second. I went to the hotkey file and made some changes (just trying some different options, like the using the wait command and I attempted to get the game to do some other things, like the example on your website of having the character all jump at the same time). only the first two characters were jumping, and the third one was standing there like a target dummy. so I went to check to make sure it was receiving command, by bringing up the hotkeynet window and watching it while I pressed hotkeys on the server/local machine. it was not displaying any received information, the check box to show keystrokes was on, and the turn hot keys on was working as well. So after many editing and reloading attempts of the hotkey.txt file (I am wondering if the program does not like me making changes and loading a new hotkey.txt file every 5 minutes for 3 hours?), I noticed that the second computer was receiving the commands that were destined for the third machine. I decided to make a fresh hotkey.txt file and type everything in new

The result (a test hotkey.txt file) is what I copy and pasted in my last post. short and simple, using just the numpad1 and numpad2, just enough to test the setup. I exited all three instances of hotkeynet (all three pc's) and reloaded them, server/local first and teh remote/clients last. everyone started up and connected. I loaded the new hotkey.txt file into the server/local machine's instance of hotkeynet. (again hotkeynet is running 1 time on each of 3 pc's). when I loaded the hotkey.txt file I got the popup that lets you know if it loaded successfully and any errors in your coding (I have also noticed that it changes sendpc local to sendpc 0.0.0.0) this image is also displayed in my last post. the key point here is that it has changed the IP addresses of the 2 other machines (as noted in my previous post). the commands also did not work on the other 2 machines.

If you look at the fourth picture in my last post (I know they are really hard to see here, but you can click on them to make them larger, as they are hosted on another website) It shows the second PC receiving the commands for both itself and the third PC, the third PC does not receive anything and the received area remains blank. so it would seem to me that the program sent all data in the hotkey for numpad 1 to the first ip address it came across. Is this normal for the data to all show up on the one computer as data received :?:

to answer some of your assumptions, all 3 computers are on the same network, and although 2 are laptops, I have all three systems directly connected to the same router, none are using wireless networking. I used the what is my IP button to find the IP for the hotkey.txt files and verified it by clicking the connected computers button on the server/local machine.

I have since gone back to running all three instances of WoW on the same PC, and have much fewer problems. once in a while I have an issue with the third instance of WoW not responding to a key press, but very rarely. I have added a wait 800 between the commands and that seems to help as I can go 20 - 30 mintues without any issue (I think these are not hotkeynet issues, but WoW issues). :?: I was also wondering if you think it is a better idea to issue the command <send pc local><sendwin wow><1><restore> instead of <send pc local><sendwin wow>1<restore> in a hotkey. it was something I noticed last night when looking over the examples on your website (I did notice the update to the reference section, thank you for that, I believe I will use the key down and key up commands and the mouseclick) there was an example posted that had the #1 in <> after the sendwin command.



this is more of an update than any additional questions, but just some info I thought I'd share before I forgot it. going to go play around some more now. I have been switching between running all 3 on 1 laptop attached to a 42" LCD TV, and 2 on 1 laptop and 1 on a pc with no TV. I find it a wee bit easier to play when using two computers, but more fun on the big screen!!! :thumbup: :thumbup: :thumbup:

:!: here is what I am using at this time as my hotkey.txt file when playing on 1 laptop 3 instances of the game, I play in a window called World of Warcraft and send the commands to the other two windows wow and wow2. I have a good 90%-95% success rate with this file and this setup, and since I like playing on the bigger screen, I may stick with it.

<hotkey ctrl 1>
<sendpc local>
<sendwin wow>
1
<restore>
<wait 800>
<sendwin wow2>
1
<restore>
<hotkey ctrl 2>
<sendpc local>
<sendwin wow>
2
<restore>
<wait 800>
<sendwin wow2>
2
<restore>
<hotkey ctrl 3>
<sendpc local>
<sendwin wow>
3
<restore>
<wait 800>
<sendwin wow2>
3
<restore>
<hotkey ctrl 4>
<sendpc local>
<sendwin wow>
4
<restore>
<wait 800>
<sendwin wow2>
4
<restore>
<hotkey ctrl 5>
<sendpc local>
<sendwin wow>
5
<restore>
<wait 800>
<sendwin wow2>
5
<restore>
<hotkey ctrl 6>
<sendpc local>
<sendwin wow>
6
<restore>
<wait 800>
<sendwin wow2>
6
<restore>
<hotkey ctrl 7>
<sendpc local>
<sendwin wow>
7
<restore>
<wait 800>
<sendwin wow2>
7
<restore>
<hotkey ctrl 8>
<sendpc local>
<sendwin wow>
8
<restore>
<wait 800>
<sendwin wow2>
8
<restore>
<hotkey ctrl 9>
<sendpc local>
<sendwin wow>
9
<restore>
<wait 800>
<sendwin wow2>
9
<restore>
<hotkey ctrl 0>
<sendpc local>
<sendwin wow>
0
<restore>
<wait 800>
<sendwin wow2>
0
<restore>
<hotkey ctrl minus>
<sendpc local>
<sendwin wow>
-
<restore>
<wait 800>
<sendwin wow2>
-
<restore>
<hotkey ctrl equals>
<sendpc local>
<sendwin wow>
=
<restore>
<wait 800>
<sendwin wow2>
=
<restore>

Quote:

---

If you look at the fourth picture in my last post ... It shows the second PC receiving the commands for both itself and the third PC

---

Ah, okay, that's all I needed to see. That picture shows PC 2 receiving <sendpc> for the other PC. That shouldn't happen. Can you please email me the hotkey file with the definition that results in that picture? I need to see the actual file because this probably has something to do with the binary contents of the file. Thanks.

Also, what program did you use to edit and save the hotkey file?

Quote:

---

I was also wondering if you think it is a better idea to issue the command <send pc local><sendwin wow><1><restore> instead of <send pc local><sendwin wow>1<restore> in a hotkey.

---

The only difference is that the program processes 1 a tiny bit faster than <1>. That's why I leave out the <>'s whenever i have a choice. But the difference is very small -- a fraction of a thousandth of a second.