Mouseclick command doesn't check if mouse is already pressed when activating
Posted: 14 Oct 2017, 08:01
Lets say I have two browser pages set side by side. on the left side I have an open page that I automated via an AHK script that uses mouseclick every now and then (about 10 minutes)
On the right side I am actively doing something.
If the click on the left page happens while I am holding down the mouse button on the right page for some reason (typically, because I am clicking something at the moment, yes even though a click is fast, it is still long enough to cause this issue). than it will effectively drag my current page over from the right page to the left page. causing the browser on the left to navigate away to the same address as the page on the right.
Over the last few days it happened to me many times. with multiple sites.
I think the solution would be to do a check to see if the mouse is currently clicked and if it is then delay or skip. Maybe default to skip with an option to change behavior to wait instead
A similar issue is if I happen to be moving the mouse when AHK tries to click a spot. Because I am actively moving the mouse when AHK triggers, AHK will often miss the the spot it is programmed to click.
For that the solution would be to check to see if the mouse is currently moving. and again, either skip or wait. and/or have the mouse input be disabled, execute the command, and then reenable mouse input.
Honestly, mouseclick (not mousemove) should probably also automatically record the current location and then return to it when its done clicking before reenabling user mouse control.
On the right side I am actively doing something.
If the click on the left page happens while I am holding down the mouse button on the right page for some reason (typically, because I am clicking something at the moment, yes even though a click is fast, it is still long enough to cause this issue). than it will effectively drag my current page over from the right page to the left page. causing the browser on the left to navigate away to the same address as the page on the right.
Over the last few days it happened to me many times. with multiple sites.
I think the solution would be to do a check to see if the mouse is currently clicked and if it is then delay or skip. Maybe default to skip with an option to change behavior to wait instead
A similar issue is if I happen to be moving the mouse when AHK tries to click a spot. Because I am actively moving the mouse when AHK triggers, AHK will often miss the the spot it is programmed to click.
For that the solution would be to check to see if the mouse is currently moving. and again, either skip or wait. and/or have the mouse input be disabled, execute the command, and then reenable mouse input.
Honestly, mouseclick (not mousemove) should probably also automatically record the current location and then return to it when its done clicking before reenabling user mouse control.