Skip to content
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

Ventura 13.6 update - no longer recognizing cliclick codes #172

Open
kjlaf21 opened this issue Sep 29, 2023 · 3 comments
Open

Ventura 13.6 update - no longer recognizing cliclick codes #172

kjlaf21 opened this issue Sep 29, 2023 · 3 comments

Comments

@kjlaf21
Copy link

kjlaf21 commented Sep 29, 2023

Anyone else having issues since updating to Ventura 13.6?

Ever since I updated a code I use no longer works. Error in terminal is : Unrecognized action shortcut “RC” in “RC:555,650”

The segment of code it is in:
tell application "System Events"
keystroke "cliclick rc:555,650"

thx

@spacestierman
Copy link

Also running into this. Attempts to run the cliclick binary just result in command not found on Ventura 13.4.

@wfaulk
Copy link

wfaulk commented Jan 22, 2024

It looks like something is upper-casing your argument to cliclick. Actually, probably your whole argument to keystroke. Is it possible that your capslock is being turned on while Applescript is sending those keypresses?

I do have to wonder why you're sending keypresses to an application (I'm guessing a terminal application) to run cliclick, though. If you need Applescript for some other reason, you should be able to use click at {555,560} directly in the Applescript (though I guess you'd have to Ctrl-Click using key down control and key up control), and if you don't need Applescript, there's surely a better way to start cliclick. There's even a better way to start cliclick from within Applescript: do shell script "cliclick rc:555,650" would make more sense.

@BlueM
Copy link
Owner

BlueM commented Feb 5, 2024

@wfaulk: thanks for your explanations on @kjlaf21’s problem.

@spacestierman: this is unrelated to the problem described by @kjlaf21. If you get this when executing something like do shell script "cliclick p" in AppleScript, you should use the full path, for instance do shell script "/usr/local/bin/cliclick p". You will get the correct path (/usr/local/bin/cliclick might not be the correct one on your system) by executing which cliclick in Terminal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants