AutoHotkey Community

[bblum]

I'm running v. 1.0.30.4 on a IBM Thinkpad R51 xp sp2. I use it to remap my Ralt to Rwin, my rCtrl to del, and the 'forward' and 'back' keys to home and end. It really makes me much happier w/ my keyboard, but I am having an intermittent problem that is quite annoying. Periodically, the system acts as if a ctrl key were stuck down. If I shut down autohotkey and my other applications, somtimes after a few minutes, it recovers, but it's very inconvenient. As far as I can tell, it only happens w/ autohotkey running. I'm going to install the latest version today, but I've had this problem with one earlier version also, and I didn't see anything in the changelog addressing this. Any suggestions/workarounds?

Bruce

[Chris]

If you could post the section of your script that remaps the keys in question, that would help. Also, if you know a series of keystrokes or window activations that a user could do manually to reproduce the problem, that would be ideal.

In the meantime, one thing that might help when the keys get stuck is to press and release the Control key, which should reset it without even needing to restart the script.

[bblum]

Thanks for the reply.

Here's my script:

#singleinstance
#installkeybdhook
#notrayicon
#usehook

!Browser_back::send, !{home}
!Browser_forward::send, !{end}

^+Browser_back::send, ^+{home}
^+Browser_forward::send, ^+{end}

+Browser_back::send, +{home}
+Browser_forward::send, +{end}

^Browser_back::send, ^{home}
^Browser_forward::send, ^{end}

Shift & rctrl::send, +{Del}

Browser_back::send, {home}
Browser_forward::send, {end}

rctrl::send, {del}
^!rctrl::send, ^!{del}

*RAlt:: ; The asterisk makes the remapping more complete on XP/2k/NT.
Send, {rwin down}
keywait, ralt
Send, {rwin up}
return


Unfortunately, I have not found any set of keystrokes that seem to 'produce' the problem, and pushing ctrl does not reset it. I've even used windows accessibility to look and see if any keys are 'down' and it does not show them as 'down.' Is there anything else that I should look for in the logs that might help?

Bruce

[Chris]

When the key sticks, do you mean that: 1) unwanted CTRL hotkeys fire; or 2) the active window behaves as though the control key is down?

If it's the second one, I've seen that happen sometimes when the active window is deactivated while the CTRL key is down. Later, when you return to that one particular window, it might still think the CTRL key is down because it wasn't watching when you released it.

If the entire system thinks the CTRL key is stuck down, you might try using the following hotkey whenever it happens. Near the top of its window, it will show you what modifier keys are logically vs. physically down:

*ScrollLock::KeyHistory ; Press ScrollLock to display the key history window.

Finally, there's a way to remap keys a lower level using the registry. Although this change is semi-permanent -- meaning that a reboot is required to undo it -- it is a very pure way of remapping that should avoid any possibility of sticking keys.

[bblum]

When the key sticks I mean 3) the entire system behaves as though the ctrl key is down, every window, the desktop, you name it!

Thanks for the tips. I don't mind the hotkeys being semi-permanent--unless they stick--because I use them all the time.

I'll post later if I find out what's going on more specifically. Since I updated to the latest version, I've not had trouble, but sometimes it goes for days between snags, so I'm not sure the update has changed anything.

Sure appreciate this program!

Bruce

[Imago]

I use a laptop (Dell 5150) with your software and am also experienceing stuck Control, Shift and most noticabley (because of the rapidly flashing indicator light) Caps Lock keys.

FAN BOOST.ahk

[Guest]

use WinBatch

FAN BOOST.wbt

[Chris]

There are a couple of things that might help with ControlSend:

SetStoreCapslockMode: Disables the changing of the Capslock key.

The alternate method of sending modifiers, which involves specifying something like {Alt down}f{AltUp} instead of !f. This special mode makes a difference only with ControlSend, not Send. The help file has more details.

[Guest]

thanks for the reference.

the winbatch interpreter has a 614k footprint....im just gunna go with that

cheers