If you’re running Mojave and using a scripting language which can’t itself access Signposts, Blowhole now gives you access to them.
Apple tells us not to use hard-coded colours like .black, but sets the default for scrolling text views to .black, causing text to be rendered in black on dark grey when in Dark Mode. Here’s a simple and universal fix.
The fields stored in the log have changed across Sierra and High Sierra. Analyse them on the wrong system, and you could lose content without being aware of it.
Why did accessing a popup menu suddenly start throwing an exception? And why doesn’t a super call handle this? Another Swift mystery solved.
Changes include an additional output text format, display log since the last boot, and support for Mojave’s Signposts is already present and being used by Apple.
Fire up your eGPUs, engage Dark Mode, and open Xcode: our Macs are once again going to be at the centre of invention and reinvention.
After 2 years, developers should be able to use the unified log for performance analysis, thanks to extensions and Xcode’s Instruments. Sysadmins and users remain neglected, though.
Adding sub-commands to write the contents of textboxes to the pasteboard: a simple task, but so easy to get hopelessly lost in it.
How would you compare two text files to see what differences are between them? It’s still a common task, for which FileMerge and BBEdit can be excellent solutions.
2017 was never going to be easy, and Apple had a lot of accidents over its closing months. It delivered a lot of new products, and with them a lot of new problems.