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
In OS X 10.11 (El Capitan), the click command does not work sometimes #26
Comments
Issues that contain the word “sometimes” are always difficult – both to investigate and to fix. Some questions:
And finally: what makes you think that the click is “initiated but not released”? |
1.) The application is a Cocoa Based application. It is a very extensive custom application with multiple controls. And I said the click is “initiated but not released” because the cursor moves to that location, the button turns blue, but the action does not take place. |
Sounds a bit like a timing problem, i.e.: things could be happening too fast. To narrow down the problem, a first approach could be to use the If not, it could be worth trying to clone the project and make the following two additions in your local copy:
This will make cliclick slow down between “clicking” the mouse button and releasing it. If the problem is still there, you could try increasing the number (which is the number of microseconds to wait) and see if it changes anything. |
Ok, Thanks. I'll try this and let you know. The help was much appreciated. |
I've experienced a very similar problem when trying to use cliclick to alt-click on the notification center icon to toggle do not disturb mode. I used the following command: cliclick -r kd:alt c:1890,10 ku:alt It did not work reliably until I applied the change in the above comments. Now it works perfectly - thanks |
Closed, as the author of the original issue did not respond within 11 months. |
I'm using c:x,y to click on an application control, but it does not click on the location sometimes. It seems like the click is initiated but not released. I have used cliclick with OS X 10.9 and 10.10 as well but there was never such an issue. Can you help m fix this?
The text was updated successfully, but these errors were encountered: