AutoHotkey Community

Hi,

I noticed that when sending a ControlClick with U option (button UP), all other buttons got automatically released. A quick check at the source revealed this comes from this line (script2.cpp:2207)
The wParam is forced to 0 hence releasing all the buttons. To fix it, simply replace the 0 with a wParam value that reflects the real states of the other buttons. Testing with pure window messages confirmed it's enough to make it work as expected.

Thanks

This would be a post message error, not ControlClick

Vh_ wrote:This would be a post message error, not ControlClick

Uh. I don't think so.

zebluk wrote:

Code: Select all

PostMessage(control_window, msg_up, 0, lparam);

The wParam is forced to 0 hence releasing all the buttons. To fix it, simply replace the 0 with a wParam value that reflects the real states of the other buttons. Testing with pure window messages confirmed it's enough to make it work as expected.

I've always used 0 also. ControlClick and the WM_ messages are used to virtually send the clicks, compared to regular Click which is more like a physical mouse action. How would you GET the states of the other buttons to know what to even pass? Would GetKeyState suffice? And if so, would you use the Logical or Physical state?

Lastly, I think this could be considered as something that would 'break' scripts so this would probably be in consideration for AHK v2

Can you provide an example? I tried something with ControlClick UP and it didnt interfere with other keys

I haven't tested the original Bug Report so I don't know if in fact it is true or not