The out-of-whackishness that I was seeing was caused by our own portable code which stored the current doc dirty state in a global. AUGH!! Yes, a global. *I* didn't write it that way. :) Anyhoo, it was preventing the document from ever being dirtied again. So to sum up, upon pausing autosave I explicitly tell it to autosave if needed via autosaveWithImplicitCancellability, in writeToURL return NO and set a userCancelled error if autosave is paused, and in hasUnautosavedChanges return NO if autosave is paused. This seems to handle all the cases I've tested so far. Thanks for the input, everyone.
-- Steve Mills office: 952-818-3871 home: 952-401-6255 cell: 612-803-6157 _______________________________________________ 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
