AutoHotkey Community

Unless I'm mistaken, GetKeyState isn't working right.. I'm using this code:

Loop {
Dn:=GetkeyState("RButton","P")
IfEqual,Dn,0, Break
}
Click

I do a right click which is detected by a different script that starts the script with the code above. I keep holding the right button down. But GetkeyState returns 1 as if the button was up, loop terminates and the gui receives a click.

If the shortcut that launches the gui and the loop is in the same script, GetkeyState works fine.

My goal is to press right button down, hold it and choose a button then release the button and get the button pressed. I need to keep the shortcut in a separate script that will choose any of the number of other scripts based on which window is active.

Is there any way to avoid putting this all in one script? Thx..

[edit]: I also tried sending a {RButton down} just before the loop, thinking that should trick ahk into seeing that rbutton is, in fact, physically down. But that didn't work either, it doesn't click right away but it fails to recognize later on that right button is released and end the loop. IOW instead of ending loop before it should, it doesn't end it even after it should.

_________________
-AK

This works OK for me on WinXP SP1:
Or this too:

The way you use it, it works because the right button is pressed while the script is running. That works for me, too. The problem comes up when the button is pressed and held before the script runs; then I run the script, use either of the examples you give and it fires off as if right button was up when in fact it's still down.

Looks like the script waits for the button to be pushed down, then it marks its state as down, and when it receives message that button was released, it sets its state as being up. However, if it's already down when the script starts, it thinks it's up; when you release it, it's either not waiting for the message at all or misinterprets it and does not act as if the button was released. That's the problem I'm having....

One workaround is to have initial button location at a spot where there's no button under it. Then that spot receives that first click and nothing happens. After that when you move the cursor to another key and release the button, it does get the rbutton up message correctly (so I was wrong above..), and clicks.

The problem with this workaround is that it's useful to put default cursor position on top of most used key (for example enter in autocad), then you could do a right click for enter, or you could hold right button and move cursor to another command and then release the button to run it.

I'm afraid I'll have to move all the code for all programs into one script..

_________________
-AK

OK, it seems your script has to work in some weird circumstances .
I hope this is your situation now. It works on the same (WinXP SP1)
It works but some funny things happening after the script has been running. E.g. my browser has unwanted behaviour when rolling the mouse wheel. Solution: There's a Send, {Rbutton Up} somewhere needed, if Rbutton was pressed before the script started. I don't know for your situation whether that Send {Rbutton Up} give some problem?

Amazing! it works, at last. And I was almost sure it's impossible. Thanks a ton . I don't really understand how it works though. I will play with it later tonight and I maybe will ask you questions.. thanks!

_________________
-AK