My bad - NSPrintInfo.sharedPrintInfo is different from NSPrintOperation.currentOperation.printInfo Cheeky! Cheers, Jay

Interesting idea - I'll give it a try and report back. Cheers, Jay

Hi Quinn, Exactly. Only crash reports with the very specific circumstances described above. I also haven't bothered open a support request with DTS for this reason - from experience this kind of incident usually goes nowhere w/o providing exact steps on how to replicate an issue.. Cheers, Jay — JayMcBee less than a minute ago

Hi Quinn, That would seem sensible. However, since a couple of macOS releases I'm getting crash reports whenever I'm updating a view: Usually it happens after e.g. adding a binding or custom transformer in version B. The crash reports then come in for version A shortly after version B has been released and refer e.g. to the binding not present in the view controller or the value transformer (introduced only in newer version B) not known in older version A. I should mention that the UI of my apps is modular consisting of 100+ .xibs (.nibs), so lazy loading appears to be in effect. And this happens reliably every time I'm updating/extending the UI. (probably affecting less than 1% of the user base but still annoying as I cannot do anything about the App Store's update mechanism) Thanks, Jay

Have you investigated the view hierarchy with Xcode's view debugger? This is commonly caused by views on top of the view in question 'eating' your mouse events.. Cheers, Jay

FWIW - I'm already using RSAppMovementMonitor (https://github.com/redsweater/RSAppMovementMonitor) but it won't detect the updater process swapping the binaries while the app is running..

Still getting frequent emails from confused customers as I have a customer base of .. casual Mac users who don't understand that the macOS Print Panel can be expanded to show additional, application specific settings. Any input from an Apple Engineer much appreciated. cheers, Jan

Ahh... the joy of Apple Help programming! Great (Nov. 2021) post on the topic: "Why won’t that Help book open?", https://eclecticlight.co/2021/11/16/why-wont-that-help-book-open/ Provides some tips when working on Help Books. I've found that copying an existing (e.g. Apple) help book and starting from there (adding content for your own app) worked best for me in the past. Even managed to enable print for (local) Help Books via reverse engineering Apple's user guides, something my users have been asking for.

Cheers - saw that before when searching, but doesn't really apply. I've ended up sprinkling my code with @available conditionals and setting min/maxSize for NSToolbarItems programmatically for legacy macOS versions (many of my users are still running for sure).

Same question here! Hellooooooo Apple - anybody home??

Same issue here! 10 months.. no answer - problems like these demonstrate why it's so much fun to create apps on macOS. Really, really sad state of affairs.

Been a while - thanks for the pointer to NSPrintPanelOptions but it doesn't help expanding the details. Note that you'd have to reset to the initial app state (e.g. by deleting the app's container) or macOS will remember if you've previously expanded the details section. My aim is to expand the details section by default starting with the first launch of my Mac app to help (inexperienced) users along finding the app specific print settings (accessory controller). Any hints appreciated, Jay

FWIW here are some screenshots that demonstrate how much the usability has deteriorated in Big Sur. Before Big Sur: imgur.com/90mR8Mm Big Sur: imgur.com/JIMF29h Any ideas on how to change this back to being usable on Big Sur..? Cheers, Jan

This is ridiculous - as a long time Mac user it's painful to see Apple slowly (but consistently) transforming from a company focussed on user experience and ease of use to a stubborn enterprise insisting on dumbing down their products across the entire line of hw and sw offerings :-(

You gotta be kidding me.. Are we holding it wrong?