Hotkeynet comming back?

Quote:

---

Originally Posted by 'Katharsis',index.php?page=Thread&postID=29513#pos t29513

So, I have been making the changes, shutting down Hotkeynet, return to text file and save changes, start Hotkeynet. Phew! I must be doing something wrong, eh?

---

You can get some rest now because I just fixed the bug that caused problems when you loaded a new hotkey file. At least I think I fixed it. :)

It should be possible now to change the hotkey file and reload it without closing HotkeyNet.

But just in case I didn't really fix the bug, please keep an eye out for it. You'll know the bug is still there if, after you load a hotkey file manually, a hotkey doesn't perform the actions you assigned to it or performs different actions.

Quote:

---

Originally Posted by Freddie',index.php?page=Thread&postID=29519#post29 519][quote='Katharsis

Feature request: A button to clear the text in the windows that show keys sent/received.

---

What's the reason for that? [/quote]

It was a casual request. While learning the program I would have the Hotkeynet window open on each computer. I would send the same command several times to see what was going on. I had the client respond with something like "Whee, it worked". After several lines got repeated it became hard to tell if a new entry had been made or not. So a button to clear the slate would be a convenience. It is certainly no problem to drag-select and delete.

I'm very pleased with the program and the well designed website with good tutorials. I'm two-boxing, using Hotkeynet with a Nostromo N52 and Multiplicity for mouse/ keyboard switching.

Quote:

---

Originally Posted by Katharsis

...So a button to clear the slate would be a convenience.

---

Thanks for explaining. I think you're right, that sounds like a good idea, so I just added a "clear" button in build 41. Let me know if it works okay.

Quote:

---

Originally Posted by Katharsis

I'm very pleased with the program and the well designed website with good tutorials. I'm two-boxing, using Hotkeynet with a Nostromo N52 and Multiplicity for mouse/ keyboard switching.

---

I'm very glad to hear that. And I'm impressed that all three things are working together (N52, Multiplicity, HKN).

Quote:

---

Originally Posted by Katharsis

Attachment 3

---

That's a great bug report, thank you very much. I just fixed that problem in the latest build, number 42. At least I think it's fixed. The program seems to connect now just about every time it starts.

Unless I've lost track, that takes care of all the bugs you reported so far. Thanks a million for your help. If you find more bugs, or have any other suggestions, please let me know.

I've got a new computer arriving today and will put Hotkeynet to the test with Vista. I haven't installed the new build yet but I did think of a couple more things.

1. The last time I clicked "About" from the menu the dialog mentioned a thirty day expiration. ?(

2. I can see where I would end up with multiple text files for different uses. It would be nice to be able to see which text file is loaded. I assume that when I load a new file it flushes the old one, yes?

3. When I want to shut down Hotkeynet I get the Hide/Shutdown dialog. Could you place a "Do not show this again" checkbox there or offer a Shutdown button next to the Hide button on the main window?

4. Here is a macro I use occasionally:

Code:

---


/console cameraBobbing 1
/console cameraBobbingFrequency 0.01
/console cameraBobbingSmoothSpeed 0.0028
/console cameraBobbingLRAmplitude 0
/console cameraBobbingUDAmplitude 10000

---

Rather than take up valuable macro space it seems Hotkeynet could handle this nicely like so?

Code:

---


<hotkey Ctrl Shift D>
<Sendpc local>
<ENTER>/console cameraBobbing 1<ENTER>
<ENTER>/console cameraBobbingFrequency 0.01<ENTER>
<ENTER>/console cameraBobbingSmoothSpeed 0.0028<ENTER>
<ENTER>/console cameraBobbingLRAmplitude 0<ENTER>
<ENTER>/console cameraBobbingUDAmplitude 10000<ENTER>

---

Just wondering if a succession of hard returns like that would be asking for trouble.

Quote:

---

Originally Posted by katharsis

I've got a new computer arriving today and will put Hotkeynet to the test with Vista. I haven't installed the new build yet but I did think of a couple more things.

---

Nice. What did you get?

Quote:

---

Originally Posted by katharsis

1. The last time I clicked "About" from the menu the dialog mentioned a thirty day expiration.

---

That only means that the particular build expires. When that happens, just go to the website and download the current build. This is a way of forcing people to run current builds, which is important for beta testing to find new bugs -- sort of a paleolithic version of an autoupdater.

Quote:

---

Originally Posted by katharsis

2. I can see where I would end up with multiple text files for different uses. It would be nice to be able to see which text file is loaded. I assume that when I load a new file it flushes the old one, yes?

---

That's a good idea. I'm planning to design a completely new interface for the program after the feature set is complete, and I'll include this idea. And yes, the old file gets flushed. (This is true today because one of your previous comments got me to fix a bug yesterday that prevented a complete flush.)

Quote:

---

Originally Posted by katharsis

3. When I want to shut down Hotkeynet I get the Hide/Shutdown dialog. Could you place a "Do not show this again" checkbox there or offer a Shutdown button next to the Hide button on the main window?

---

Yeah I'll do something about this. But I have to be careful not to do anything to confuse new users. Sometimes there's a tradeoff between ease of use for old users and avoiding confusion for new ones. Especially with this program, where there is so little visible interface, I want to be careful about that.

Quote:

---

Originally Posted by katharsis

Just wondering if a succession of hard returns like that would be asking for trouble.

---

Why would it be trouble? It's no trouble for HKN -- it doesn't care which keystrokes or how many you ask it to inject. It may be trouble for the game but I don't play WoW so I can't comment on that. (I should probably restart my WoW account to get familiar with it -- I never got past level 12.)

In general, one fact that you always need to keep in mind is that HKN injects the entire macro at lightning speed, but the game can't always accept keystrokes that fast, and some of the keystrokes may get lost. If that happens you need to insert <wait ####> commands into the macro to give the game time to get ready for the next keystroke. Placing <wait ####> commands and adjusting the number in them is a matter of trial and error.

Is there a command or something I can put in the config file to tell Hotkeynet to pause?

I can right-click on the icon when it's in the system tray to pause, I'm looking for a way to arrange it so I can press a key to do the same thing. Thanks for the help!

Quote:

---

Originally Posted by 'Darm',index.php?page=Thread&postID=29786#post2978 6

I'm looking for a way to arrange it so I can press a key to do the same thing. Thanks for the help!

---

A number of people have asked for this, and I'm going to try to add it to the program. Unfortunately, it's difficult because of the way the program is designed, and it may take me a while. Thanks for the suggestion.

Quote:

---

Originally Posted by 'Freddie',index.php?page=Thread&postID=29802#post2 9802

Quote:

---

Originally Posted by 'Darm',index.php?page=Thread&postID=29786#post2978 6

I'm looking for a way to arrange it so I can press a key to do the same thing. Thanks for the help!

---

A number of people have asked for this, and I'm going to try to add it to the program. Unfortunately, it's difficult because of the way the program is designed, and it may take me a while. Thanks for the suggestion.

---

I was thinking about this some more last night. Perhaps change it so that instead of shutting down the keyboard hook, but validates the hotkey against an active/inactive list before firing off the macro. As for incorporating that into the script, there could be a couple of ways.

<Hotkey X Switchkey> could define a single toggled hotkey, while
<Hotkeygroup Name SwitchKey> ... </Name> could encompass a group of keys with a common toggle.
To toggle on/off actual windows or instances, the Switchkey could be set in the <rename> or <rename_from_path> commands.

Finally, would there be much demand for <HOTKEYDOWN>and <HOTKEYUP>definitions? My reason is that while WoW's /follow command is cancelled fairly easily, it isn't the case in EQ2 where you can still use left & right movement to circle around your /follow target. Having to repeatedly press an arrow key to have the scout inch around doesn't feel or look very cool ;)

Call it a wishlist ;)

And for the record, I've been testing this with 2 EQ2 instances on 1 box. The <sendwin> command will work ok, but only with a sufficient <wait> (as you mentioned above with the WoW console). Natively, the <sendwinM> does not work with EQ2 but does under Innerspace (I know, I caved ;( ) That being said, I've seen some very funky key translations happening. For example, a <numpad_minus> key that injects an <equals> to both instances comes though as a <0> on the background instance. Really not sure what is happening there ?(

Cheers :)

I added on/off commands to the program today, since several people asked for them. There are three new keywords that you can use in hotkey definitions:

turn_hotkeys_on
turn_hotkeys_off
toggle_hotkeys

Of course you don't need all three. If you like the idea of a toggle, you can use that one by itself. Otherwise make a pair of hotkeys with the other two. All of these new keywords can be used on the local machine like this:

Code:

---

<hotkey F1>
    <sendpc local>
        <toggle_hotkeys>

---

or on a remote machine like this:

Code:

---

<hotkey F1>
    <sendpc 192.168.1.102>
        <toggle_hotkeys>

---

In all cases, "on" and "off" refer to whether pressing keys on the "sendto" pc will generate a macro. They do not afffect whether that machine receives macros from some other machine. If you want a pc to stop receiving macros, you need to turn HotkeyNet off on that machine.

I didn't have time to test these new keywords carefully so I'd appreciate it if you'd knock them around a bit and look for problems. Thanks.