site_archiver@lists.apple.com Delivered-To: cocoa-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=uni-bremen.de; s=2019; t=1744975968; i=@uni-bremen.de; bh=SCB2vyRKPlQS/7uMalvdhdz59H9jZ04EaYI18seqCRs=; h=From:Subject:Date:References:To:In-Reply-To; b=O36ayp6nGWjdaB2YAbCtlGOnxS8DaaxKpf3gbLi/N0QrzwfmjkAbkfGrfniprwnMr jQO5zoxFglbB1fTTO8uflpmOB65jHAFGcihBa7xJFLKqA54Xb9Ibj0JEoTAHFudSuY Asi4aX6eFmd7pYqqWw15bVPLNDUKLa27nsl5FyMmdG/fIv9L1mqlw7L4gGyDbnq9R1 6WcqO+bSg91TCS8NXdtCWhyLB6BzUpIb0EuIbj5/H2T/26fo9t3tqZYTXPhML2IdmJ hDsenPGTnoNnkNa8sAwrOonUxuFrVfH31invWSjCiYeEryYMOrnVBxdoOIf0kPzfFa KW32I+S2WzZ1A==
Looking at my code to handle the OK and Cancel actions for the config sheet, I still have these calls from way back:
[defaults synchronize]; // It says this isn't needed, but it sure seems to be for a screensaver pref,
This is what I do once the user clicks OK: [defaults_ setObject: monitor_user_prefs forKey: displayName_]; [defaults_ synchronize]; But, the 'synchronize' does not help, it seems.
I'd say try using that and see if it helps. But, exactly why and when are you writing prefs during the run of your screensaver instances?
After the user clicks OK, I do some image "harvesting", which usually takes a few seconds, then I execute the two lines from above.
Or are you only writing them during in the config sheet?
Yes, sometimes, if the user makes very small config changes, then I write the new prefs directly after the OK button. Best, Gab. _______________________________________________ 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/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com smime.p7s