I heard that the User Defaults API does caching since 10.9 Mavericks. If so, it is safe to use when adding Sudden Termination to your app?
I figure that Sudden Termination should be suspended when running save-file code, to avoid corruption. Should it also be done for load-file code? What about when a local file URL is loaded into a WebKit instance? I figure you should suspend Sudden Termination when user-important state becomes dirty, right? I load left-over web-history at app launch and save it at app terminate. Notifications at both points turn off a dirty flag. Notifications on web-history adding, removing, or completely clearing turn on that same dirty flag. Does this mean I need a timer or something to occasionally save the web-history during the program? If I add (window/app) Resume state and/or Automatic Termination, would I need to add more Sudden Termination suspensions too? — Daryle Walker Mac, Internet, and Video Game Junkie darylew AT mac DOT com _______________________________________________ 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