HotKeyNet how to use it?

[dRiN]

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

<hotkey 3> 
<sendpc 172.19.3.3> 
4

Gives the following error.

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

[Freddie]

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.

[dRiN]

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?

[Freddie]

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.

[Freddie]

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

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

[finndo]

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>

[Freddie]

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>

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?

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.

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.

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.

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.

[finndo]

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.

[finndo]

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









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.







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

[Freddie]

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.

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:

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?

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.