Hotkeynet comming back?

[Freddie]

It sort of works now... Right now it positions the mouse correctly as before, but it seems to be clicking before making the move.

I think I fixed this. It seems to be a timing problem just like the shift key issue. HotkeyNet was asking Windows to perform the move and the click in the correct order, but Windows apparently takes longer to move than to click, so EQ2 was seeing the events in reverse order.

To fix the problem, I had to insert a delay between the move and the click. This time I made the delay automatic instead of something you have to write in the hotkey file The default length of the delay is 15 milliseconds. If this is too short, you can make it longer on the Settings panel.

The fix is in build 54 which is on the site now.

Please let me know if this fixes the problem.

(I didn't forget about the MouseMove command -- I'll do it after we fix this bug, because I don't want the new command to be a substitute for a real fix.)

[kandore]

90% of the time it does them in the right order...oh wait, I increased the delay to 50 and now it works. The default was 15 and that was a little to little. I'll keep playing with it just to be sure.

[Freddie]

Thanks. What's the CPU specs in that machine? Brand, cores, GHz?

[kandore]

Main Computer (server)
AMD Athlon 64 X2 Dual Core Processor 4200+
2.20 GHz 2 GB RAM
NVIDIA GeForce 6600 in the PCI Express slot
I play w/ two monitors on my main computer and one on my older one. My gf just kicked me off the older one in order for her to do homework...so I can't give you the exact specs. It's probably 5 or 6 years old now since I got it when I was a senior in high school. I think it has 768mb of RAM and it uses some AGP card. My newer one is about 2 yrs old now. I really want to upgrade again soon. Get some SLI goodness going. EQ2 is so freakin demanding.

[kandore]

I think I ran into a problem the other night, but I'm at school now so I can't post the exact code I was using. I know it used to work a few builds ago when I first wrote the macro. Basically I tell my client computer to press key 4, wait 100ms, and then use the keydown alt/wait/key/wait/keyup method. All of my keydown and keyup commands using ctrl work fine, but this one with alt is having problems. I guess I should have tested it out more last night, but it was only affecting a minor spell and I wanted to level, hehe. If i get to play 2nite I'll post the exact code and run some other tests with alt...but if you find any issues with keydown/keyup and alt let me know. Thanks!

[Freddie]

Why don't you post it when you get home and i'll take a look at it.

[mana333]

I'm on a wireless connection and I get dropped and picked up several times a day (looking into the issue). The problem I have is that the client won't recognize that the connection has been dropped. It still reads as if it is still connected to my server when in fact it is not. The server recognizes the drop and gives the message accordingly. What I have to do is go into the room with the networked computer and manually restart hotkeynet. Is there a way to fix this?

[zuvio]

I am trying to multibox 6 ffxi accounts on two PC's, so naturally I ran into the problem of keystrokes not being broadcasted to non-active FFXI windows. HotKeyNet offers me some solution to this problem, but it's not 100%. I use the method of <sendwin FFXI account> to send keystrokes to all my running windows with the downside of having HKN switch between them and restoring afterwards.

My basic Hotkey file looks like this:

<hotkey 1>
  <sendpc local>
<SendWin Zuvio>
  <wait 70>
  <Lctrl 1>
  <wait 70>
<sendwin Carsomyr>
  <wait 70>
  <Lctrl 1>
  <wait 70>
<sendwin Aella>
  <wait 70>
  <Lctrl 1>
  <wait 70>
<restore> 

This hotkey sends the key combo ctrl+1 to all active windows. In FFXI, you access your macros through the combinations of ctrl+0-9 and alt+0-9. So all my windows active macro ctrl+1 with the hotkey 1.

So far, all the other <send> commands do not work in this game. I have tried the same macro with <sendwinM> + <SetBackgroundFocus> and <KillBackgroundFocus> and <sendwinMF>. These hotkeys do not send any keystrokes to any window. This is very annoying while playing the game because 1: it flips the windows which sucks and 2: it creates some lag in sending the commands. I would be very happy if there was some way of sending keystrokes to non-active windows simultaneously without having to flip through focus.

Are there any future plans of incorporating FFXI into the program, such as the DoaC send command? I would really appreciate that.

But for now, HKN allows me to multibox this game on two PCs, so I am extremely grateful for that already.

Macros such as this one below have no effect, they do not send keystrokes to the windows, none of them

<hotkey F1>
    <sendpc local>
        <sendwinM Zuvio>
            <setbackgroundfocus>
            <wait 100><LCtrl 1><wait 100>
            <killbackgroundfocus>
        <sendwinM Carsomyr>
            <setbackgroundfocus>
            <wait 100><LCtrl 1><wait 100>
            <killbackgroundfocus>
        <sendwinM Aella>
            <setbackgroundfocus>
            <wait 100><LCtrl 1<wait 100>
            <killbackgroundfocus> 

[Dareon]

Im finding a program that works for free and i found this post and was wondering how this works? And yes i found the guide on the websites but i really didnt get it... There you didnt tell where you should put those hotkeys etc? Im sorry im noob but im an amateur

[Freddie]

I'm on a wireless connection and I get dropped and picked up several times a day (looking into the issue). The problem I have is that the client won't recognize that the connection has been dropped. It still reads as if it is still connected to my server when in fact it is not. The server recognizes the drop and gives the message accordingly. What I have to do is go into the room with the networked computer and manually restart hotkeynet. Is there a way to fix this?

This doesn't happen on my network, so I'm going to need your help in order to try to find the cause of the problem. My first thought is that this problem could be caused by any one of three things -- my use of the Windows socket API inside HKN. or the way Windows handles socket connections, or your router. If anybody has any ideas, please chime in.

Could you do a couple of little experiments? First, start both copies of HKN. After they connect, close (exit) the server copy of HKN by clicking with the mouse. Does the client HKN correctly notice that the connection is gone?

Second, wait for the problem to occur as you describe. When it happens, instead of walking into the other room and restarting the client manually, just let the cliient run for a while. Wait for a while -- up to an hour, say -- and see if the client notices on its own that the server is gone. (The reason I'm asking you to do this is to see if it's a question of a time-out value that presumably could be set differently.)