Searching for third party Quick Actions, I came across the excellent Yoink, the only app which seems to have solved them. Or has it?
The built-in Quick Actions and those bundled in installed apps are managed by the daemon pkd, and PlugInKit. Not so Automator workflows, though.
The problem of Undo is a major consideration when building or using any Quick Action, Automator workflow, AppleScript, or other lightweight solution.
Calling command tools from Swift changes with macOS 10.13 and 10.14 with the deprecation of some of the Process class. Solutions aren’t as clean as they should be.
Can you sign AppleScript apps in Script Editor? Is there a better tool? What’s the best way to sign a command tool developed in Xcode?
Advice on preparing for and using Mojave for all who go beyond using standard off-the-shelf apps – scripting, automating, building from source, or full-blown Xcode development.
Control of one app by another is an important but difficult aspect of Mojave’s new privacy controls. Here’s how it handles that at present, and some of the issues it raises.
For many users, privacy controls in Mojave will pass almost unnoticed. Here are tips for those who have greater demands, and want their apps to access protected data.
If you’re running Mojave and using a scripting language which can’t itself access Signposts, Blowhole now gives you access to them.
Why did accessing a popup menu suddenly start throwing an exception? And why doesn’t a super call handle this? Another Swift mystery solved.