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