Requested Feature

[Vreejack]

I figured out a contributing factor. If I use the modifier keys on my mouse instead of using the keyboard this happens almost every time. Unfortunately I must use the mouse keys.

It must have something to do with the way X-mouse button control works with HKN'

Or not, as the keyboard is doing it too, just less often. has to be a timing thing.

Something to do with X-mouse generating simulated LAlt and LCtrl signals is confusing HKN. Darn subtle.

[Vreejack]

SOLUTION!

Everything works perfectly if I use SendWinX instead of SendWin.

[Bettysue]

It sounds a lot like some focusfollowsmouse is causing or could be used to fix. Odd I know but if you are using it and your mouse hits a non-hidden taskbar or random window, it can cause weird effects. If you don't use it clicking another window and a slow response time to the key can cause undesireable effects. In order to help further we would have to see your script. Just make sure you remove passwords and usernames from your script if you have them in there. Enclose the script in code tags to maintain formatting, and help out the forum mods so they don't have to do it for you.

[Freddie]

What almost always happens is that w2 never gets focus and instead the taskbar flashes a tab for w2 needing attention. Then all the keys which were supposed to go to w2 go to w1 instead. I tried inserting a delay after the first sendlabel but that did not help.

Thanks for the excellent description of what you're seeing. Here's why this is happening. When HotkeyNet sends a keystroke with SendWin to a background window, the first thing it does is tell the operating system, "Please raise the target window to the foreground." Usually when a background program makes this request (HotkeyNet is in the background), Windows refuses to do it as a matter of design to prevent background programs from taking control of your screen and annoying you. So what the operating system usually does in this situation is blink the task bar icon (as you describe) to alert you so you can decide yourself which program should be in the foreground.

Normally, when SendWin is working properly, HotkeyNet plays a sort of trick on the operating system to force it to carry out the request. In this case, based on what you describe, the trick isn't working. Delays can't help because the problem isn't caused by time. It's caused by the operating system making a decision to refuse the request.

SOLUTION!

Everything works perfectly if I use SendWinX instead of SendWin.

Glad to hear it.