On Nov 29, 2015, at 15:44 , Ben Kennedy <b...@zygoat.ca> wrote: > > although it does not mitigate the actual insidious destruction which I want > to believe, as Quincey postulated, is only a bug rather than deliberate > design).
Well, it turns out that I’m absolutely wrong. I just checked the documentation: https://developer.apple.com/library/prerelease/mac/documentation/DataManagement/Conceptual/DocBasedAppProgrammingGuideForOSX/StandardBehaviors/StandardBehaviors.html#//apple_ref/doc/uid/TP40011179-CH5-SW3 <https://developer.apple.com/library/prerelease/mac/documentation/DataManagement/Conceptual/DocBasedAppProgrammingGuideForOSX/StandardBehaviors/StandardBehaviors.html#//apple_ref/doc/uid/TP40011179-CH5-SW3> (It was last updated in 2012, so this is not some new change.) Autosave-in-place *is* supposed to update an already-saved document in place. There is no separate autosave, and the correct way to go back is to use the versions browser. There is also no “Don’t Save” button in a do-you-want-to-save dialog. It’s a “Revert Changes” button instead. The “don’t save” concept has just gone away in such apps. Either I never knew this, or I knew this but forgot since the last time I worked on an autosavesInPlace==YES app. _______________________________________________ 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