In Sierra but not Mojave, when the user opens an ancillary window, it appears for a moment, then vanishes. Is it a bug in the code, or in AppKit?
A simple way to provide a proper Help book for your app, and separate PDF documentation without wasted effort. Uses Swift in Xcode.
By popular request, how to customise the PDF reader’s interface to enlarge the window and show larger thumbnails. With two lines of code.
Searching for third party Quick Actions, I came across the excellent Yoink, the only app which seems to have solved them. Or has it?
This second part uses Xcode’s Interface Builder to create the document window, then wire it up to the code which brings PDFKit and AppKit together.
Building a useful app in Xcode 10.1 with Swift. This app is a PDF reader which requires around a dozen lines of code.
Unsupported by developer documentation or Xcode, Quick Actions can only be seriously useful when reversible. Or are they just an embellishment to Finder?
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.