Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

Windows / Bug in Windows AGK Tier 1 - v1.08.24 Using Message & Keyboard (GetRawKeyState)

Author
Message
Abiz
6
Years of Service
User Offline
Joined: 14th Nov 2012
Location: Amsterdam
Posted: 12th Nov 2014 19:24 Edited at: 12th Nov 2014 19:25
I want to report a bug in the software based on below code. (totally simplyfied)

Basically the bug is this: Hold cursor right (or any key) and then throw a message(). Upon closure of the message the state is still on, even though you have released the key.
It does not process the release of the key, since message interrupts all flow (I assume).

Here is example code that gives the error with full instructions on how to reproduce the error.

Thanks for a great tool, so please see this not as criticism, but an effort to help make it even better.

Naphier
8
Years of Service
User Offline
Joined: 2nd Oct 2010
Location: St Petersburg, Florida
Posted: 19th Nov 2014 11:27
It's a problem with the message box.
Message boxes tell the app that it was sent to the background which interrupts capture of key presses/releases

So instead of using the message() command do this:

done = 0
repeat
Print("...stuff...click to dismiss")
if GetPointerPressed() = 1 then done = 1
sync()
until done = 1

you also need to set counter = 0 when counter = 50 otherwise it is going to get stuck in that conditional.

Login to post a reply

Server time is: 2019-07-22 02:25:38
Your offset time is: 2019-07-22 02:25:38