MartinLichtblau
commented
5 years ago Finally I found the cause of it and a fix for it. Keys become stuck because the event for key down is called after the key up event and thus the SendKeyEvent fires down although the key is already up and the respective event already fired. This can happen with such a simple construct:
LAltEvent(state) {
if(state) {
AHI.SendKeyEvent(kbdId, lShiftSc, 1)
} else {
AHI.SendKeyEvent(kbdId, lShiftSc, 0)
}
}This likely happens because both up and down events happen roughly at the same time and AHI handles these events in the wrong order. I guess that thread pooling and calling is responsible for it. You could also say that the keyboard key repeat function is the culprit. The best indicator I found is that the A_Tickcount for the up and down event is identical.
Therefore the solution is to fire the down event only if the tickcount of the up and down event is different.
LAltEvent(state) {
static LAltEventDownTime, LAltEventUpTime
if(state) {
LAltEventDownTime := A_Tickcount
if (LAltEventDownTime != LAltEventUpTime) {
AHI.SendKeyEvent(kbdId, lShiftSc, 1)
}
} else {
LAltEventUpTime := A_Tickcount
AHI.SendKeyEvent(kbdId, lShiftSc, 0)
}
}
evilC
I have remapped all modifier keys with AHI, for instance Alt is Ctrl now. But too often I get stuck keys, pressumably when pressing multiple modifier keys at the same time. Could it be that AHI's ability to block inputs is causing this? E.g. when a key is physically released while the input is blocked.