New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move cursor back to avoid accumulated movement #411
base: master
Are you sure you want to change the base?
Conversation
Code Climate has analyzed commit b37d66b and detected 0 issues on this pull request. View more on Code Climate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There needs to be a short delay between the 2 from what I have seen. adding time.sleep(0.04)
between the 2 should do the trick. Other then that It looks good.
I’ve seen the |
it's a 40 millisecond delay. I am fairly sure it is there so that the Windows notification system is able to make it's callbacks before the next move takes place. I know that If you use the Move Mouse action and you do not put a wait and then add the action to click a mouse button, it doesn't work properly but if you add a wait in between the 2 everything works. If it was a semi long delay I would be concerned with it but being that the delay is only 40 milliseconds I am not concerned with it. |
also you need to push the commit with the changes for the delay in order for them to be added to the PR |
In my tests the delay was not needed, but it was requested here: EventGhost#411 (review)
972-master completed (commit 4a2a2ee2a4) |
Fixes #410