On Nov 27, 2013, at 11:53 , Graham Cox <graham....@bigpond.com> wrote:
> in many cases I’m afraid “trashing the prefs” is akin to voodoo as a solution > for a problem, but it’s often put out there (not by us if we really don’t > think it will help I hasten to add). > > Adding a button it is, I agree it’s better all round FWIW I would say: right diagnosis, wrong solution. What on earth is going on with your app(s) that requires preferences to be deleted? If, after all these years of your being a very accomplished developer, your apps aren’t robust enough to deal with unusable or inconsistent values in prefs — or, more to the point, put the prefs into such a state to begin with — then I humbly suggest you treat that as a major bug, and fix it. It’s certainly true that there have been been scenarios in the past where some condition external to your app code could cause a corruption — e.g. a crash — but I think you can look at the new Mavericks caching as Apple’s side of a commitment to avoiding that. Now, a crash or sudden termination in your app can’t corrupt the prefs, since the user defaults daemon doesn’t crash too. Is there a genuine reason why you can’t robustify your app’s dealings with preferences, and avoid the entire problem of deleting them? _______________________________________________ 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
