How to reliably unstuck ctrl alt and shift ( not just by send() )

[imNew]

due to the nature of what I am doing, my keys will get stuck, unavoidable, I just need a reliable _clearKeys()

My observation so far:

send(key up) works ALL the time for normal keys, ie. asdf's

same can't be said for ctrl alt and shift

in a simple ctrl click:

send("{ctrldown}")

for $ i = 0 to 4

mouseclick("left", 11, 11)

next

send("{ctrlup}")

in my particular instance, send("{lctrl down}"), send("{lctrldown}"), send("{ctrl up}"), send("{lctrl up}"), send("{lctrlup}") do not work or they will not free the ctrl key at the end.

only send("{ctrlup}") works, but not always either.

in severe cases, even a send ("ctrl") will get the ctrl key stuck (SendKeyDownDelay=30 or higher)

What I am afraid is that, once the ctrl key is stuck in down position, all the subsequent send(key) will be interpreted as send(ctrl+key), EVEN the send( ctrl up) attempts.

I would like a function that is lower level, something like _isPressed("12"), that can just clear all the "down" keys.

my system is x64 windows 7.

Edited January 31, 2013 by imNew

[Danp2]

You might want to read this FAQ entry.

FWIW, I've been using the following with good success:

Send("{SHIFTUP}{CTRLUP}{ALTUP}")

[nitekram]

Just asking a question - is it possible to fix this? I know there is a work around in place - a few in fact. But just wondering if we can change the function/code to change the status of keys to what they were before this command Send() was used with the shift, ctrl, alt keys.

[JohnOne]

or more precisely http://www.autoitscript.com/wiki/FAQ#General_unstuck_method

[imNew]

thanks a lot for the pointer. I will look at it more serious now.

I m assuming ControlSend("","","","",0) won't work right? some key, any, has to be controlsent in order for that to work.

[PhoenixXL]

why not use _Winapi_Keybd_event, twice

once for pressing the key and the other for releasing it,

I havent noticed any problems with it yet

[JohnOne]

thanks a lot for the pointer. I will look at it more serious now.

I m assuming ControlSend("","","","",0) won't work right? some key, any, has to be controlsent in order for that to work.

Why would you assume that even with it being in the FAQ as an answer?

Perhaps they just put it there for a laugh.

[imNew]

well, mostly because in ideal conditions, ie. testing in textpad, send (key up) operations will always free my keys, don't even need the controlSend.

However I encounter loads of problems when the stuff I am trying to interface with doesn't register key presses in an orthodox way and there are delays as well. That's why after trying FAQs once without any breakthru, I gave up and came on the forum. Apparently the FAQ is the best solution, then I have to try to make it work.

[JohnOne]

I just meant, you should not assume anything when all you need to do is test it.

I have no idea why it works, I just know that it does.

[Melba23]

imNew,

I note your original post read:

"in my particular instance (a game environment), send("{lctrl down}"), send("{lctrldown}"), send("{ctrl up}"), send("{lctrl up}"), send("{lctrlup}") do not work"

I also note that you have amended this without being prompted - but please read the Forum rules (the link is also at bottom right of each page) - particularly the bit about not discussing gane automation - before you post again.

The fact that you are trying to use AutoIt in a game is undoubtedly why you are having these problems - therefore there seems little point in continuing with this thread. And so......

M23