Mike D

I notice that some of the sample code calls .loadWindow() on the Preferences window controller. Example: https://github.com/soffes/Clock.saver/blob/main/Clock/Classes/MainView.swift#L24 Apple says > You should never directly invoke this method. Instead, access the...

> Historically closing the sheet has been a mess as there are few solutions that work accross multiple macOS versions Agreed. In earlier OS's you could do this: ``` override...

Interesting. Here's what I'm doing: * the Helper app is inside the .saver bundle, located at : Example.saver/Contents/Helpers/Helper.app * the helper app reads/writes data to/from `~/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Preferences/com.example.plist `(or) `~/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver.x86-64/Data/Library/Preferences/com.example.plist `when running...

Clearly, the best outcome would be if Apple: * fixed the bug * gave us documentation / sample code showing how to do a Swift screensaver correctly * published the...

> * Does WKWebView2 require some specific entitlement ? I think I tried using it at some point though that wasn't on Aerial I think, and had issues. Have not...

I agree, those 2 issues (crash after close the settings panel, double-click .saver file) seem fixed in Beta 3. Regarding CFPreferences : I think I'm doing the opposite of what...

Perhaps using a relative path with "~" doesn't work? I had to go back and untangle my code, but here's what I'm doing to read from inside the Sandbox from...

Also, if your App and .Saver are Intel, you would need to replace **legacyScreenSaver** with **legacyScreenSaver.x86-64** when running on a M1 system.

Glad to be of help!

I'd be interested in pursuing some other quality-of-life issues with screensavers on Ventura. I've pretty much given up on the ability to capture Keyboard events on Catalina or higher, but...