Rpow Posted January 19, 2008 Posted January 19, 2008 Sometimes Windows programs fall behind in processing keystrokes, so keystrokes, particularly repeating keystrokes, such as those for arrow keys for scrolling/panning, can load the keyboard buffer. This causes a sort of "run on" effect, after the user terminates the repeating action.It would be great to have an au3 script that could interrogate the Windows XP keyboard buffer to determine if it is empty. This technique could be employed whenever rapid, repeating keystrokes are being used. The user could interrogate the keyboard buffer to see if it is empty just before sending each repeat keystroke. Each such keystroke would be sent only if the buffer is empty. Then, when the user stops sending the repeating keystrokes, action would stop quickly because there would be, at most, only one keystroke in the keyboard buffer.Thank you for considering this question.Rpow
Thatsgreat2345 Posted January 19, 2008 Posted January 19, 2008 It is most likely possible through some DLL Call, good luck, and report your findings.
Rpow Posted January 19, 2008 Author Posted January 19, 2008 It is most likely possible through some DLL Call, good luck, and report your findings.Thanks Thatsgreat2345. I have been experimenting using a DLL call to GetQueueStatus with flag = QS_ALLINPUT but with no success to date. QS_KEY seems the more intuitive flag, but apparently reflects only a few special keys.I am a beginner, so I may have some format problems; or my selection of GetQueueStatus for this purpose may be erroneous in the first place.http://msdn2.microsoft.com/en-us/library/ms644940.aspxRPow
Thatsgreat2345 Posted January 20, 2008 Posted January 20, 2008 Thanks Thatsgreat2345. I have been experimenting using a DLL call to GetQueueStatus with flag = QS_ALLINPUT but with no success to date. QS_KEY seems the more intuitive flag, but apparently reflects only a few special keys.I am a beginner, so I may have some format problems; or my selection of GetQueueStatus for this purpose may be erroneous in the first place.http://msdn2.microsoft.com/en-us/library/ms644940.aspxRPowFeel free to post any code you have created and many people will gladly help correct you. Even if your code is wrong we much rather correct wrong code then make it all ourselves.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now