quick question:
how would one script a command so that ' w ' is sent to the other window until the ' w ' key is released
ie: i want both of my characters to move at the same time w/o using a follow command
quick question:
how would one script a command so that ' w ' is sent to the other window until the ' w ' key is released
ie: i want both of my characters to move at the same time w/o using a follow command
You can't yet, but it's on the list of things to add.
�Author of HotkeyNet and Mojo
Build 48 is now available. New stuff:
-- Mouseclicks. You can now make hotkeys that click windows or the screen. There are many options for positioning the clicks.
-- The bug that caused single keynames like <F3> to be mistranslated with SendWinM and SendWinMF has been fixed. (However you still cannot use multiple keynames like <ctrl F3> in output. I'll fix that soon.)
More info about MouseClick here
Download HotkeyNet 48 here
�Author of HotkeyNet and Mojo
Hi Freddie.
I quickly tried build 48 and <sendwinMF> with EQ2 last night, but that still doesn't work. Does <sendwinmf> require <set_backgroundfocus> too?
Thanks for testing that and letting me know.
You don't need background_setfocus with SendWinMF because it's already built in. (SetWinMF consists of SendWinM, background_setfocus, and background_killfocus combined in a single command. The F stands for focus.)
I'm not surprised to hear that SendWinMF doesn't work with EQ2. When I wrote that command, I had DAOC running, and I kept testing different combinations of Windows API functions until I found one that works with that game. But I wouldn't necessarily expect it to work with any other game. In order to stand a chance of creating commands that work with other games, I probably have to do the same thing individually with each one.
�Author of HotkeyNet and Mojo
Oh good, someone else is using this with EQ2. Have you had any issues with keydown and keyup? When I try to use anything that requires my other pc to hold down a key nothing happens. The copy of hotkeynet running on my other computer shows that it received the command and the keys it's pressing, but my game doesn't do a thing.
I have some decent macros taking up the number keys but it would be nice if I could use the whole range of the hotbar. Hopefully this is just me and maybe installing the newest version will fix it.
I'm working on that stuff right this minute. There will be a new build soon. I made a mistake when I told people to use <KeyDown> and <KeyUp>, because when I started working on them again yesterday, I realized that they were incomplete in the versions that are on the website. In those versions, at best, they will only work with SendWin. Sorry for my mistake.
Like I said, there will be a new build soon with all this stuff (KeyUp, KeyDown, and combo keys like <shift alt F3>) workng with all Send commands.
�Author of HotkeyNet and Mojo
Woohoo, thank you. I definitely appreciate all of the work you're putting into it. I look forward to the future builds![]()
The new build (49) is now on the website. I decided to do this work in two stages. First for SendWin, then later after this first round of changes is debugged, I'll do the other Send methods.
I had to change a lot of code internally, so I probably created some new bugs. It would be really helpful if people would download the new build and kick the new stuff around a bit to flush the bugs out. Changes include:
(1) You can now use multiple key labels like <ctrl F3>, <rshift lalt 7>, etc., for output.
(2) Added <KeyDown scancode ex> and <KeyUp scancode ex>. The purpose is to give the user exact control over which key gets output.
(3) Fixed <divide> bug.
A note about the first change. While I was testing it, I found that HKN types keystrokes so fast that some programs don't have time to see the shift keys. With DAOC, for example, instead of writing this:
<shift 2>
I had to write this:
<keydown shift><wait 100>2<wait 100><keyup shift>
...just to slow things down enough for DAOC to see all the keys. But with other programs, <shift 2> works fine.
�Author of HotkeyNet and Mojo
I played with the newest build for a few hours tonight on EQ2 and I didn't run into any problems. I did have to use the <wait> method with the keyup and keydown commands, but it did work. Thanks for the super quick update.
Connect With Us