> > My screensaver has never experienced this problem with any OS version.
Interesting!
I was losing hope ...
I seem to remember that about 2 years ago a few other people on this list
experienced something similar as I did ...
> You *are* using the correct NSUserDefaults object, right?
> [ScreenSaverDefaults defaultsForModuleWithName:@"your module name"];
Right, here is what I do:
defaults_ = [ScreenSaverDefaults defaultsForModuleWithName:
@"de.zach.ArtSaver"];
NSDictionary * monitor_user_prefs = [defaults_ dictionaryForKey:
displayname];
NSNumber * fontSize = [monitor_user_prefs valueForKey: @"FontSize"];
fontSize_ = [fontSize unsignedIntValue];
etc.
> I've mentioned this to you before, but what I'm guessing is happening is that
> your screensaver is experiencing the same thing that all legacy screensavers
> are seeing, which is that they no longer get stopped when the user wakes the
> screen. The process named "legacyScreenSaver (Wallpaper)" loads and runs your
> screensaver views, but they broke it some time back, and it no longer tells
> them to stop. This is very easy to see by looking at all processes in
> Activity Monitor. Start and stop the screensaver multiple times and you're
> bound to end up with multiple instances running for every screen. I've added
I don't see this on my side.
I have let macOS launch my screensaver several times,
but still I see exactly one process:
legacyScreenSaver (Wallpaper)
Also, I don't see any process "ArtSaver" (the name of my plugin).
Best regards,
Gabriel
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
