On 2013 Apr 22, at 21:42, Steve Mills <smi...@makemusic.com> wrote: > [-setAutosavingDelay:0.0] didn't work.
OK, then. I retract my surprise. > The pause mechanism is something in our own code - a bool that says it's > paused (it's actually an integer so it can be incremented/decremented in a > nested fashion). That's fine, but your code is not running the show in Lion autosave. The holy grail we're discussing here is a method to tell Cocoa "Stop sending me autosave requests (-[NSDocument autosaveWithImplicitCancellability:completionHandler:]) until I tell you to start again". I believe, as I have from the beginning, that there is no such method. If your NSDocument subclass returns YES to +autosavesInPlace, you *will* get (-[NSDocument autosaveWithImplicitCancellability:completionHandler:]) at arbitrary times. > I check this value in writeToURL and hasUnautosavedChanges. I've never tried -hasUnautosavedChanges, because it's another "Tiger" autosave method, available since Mac OS X 10.4. Do you ever get that message? If so, then returning NO might pause -[NSDocument autosaveWithImplicitCancellability:completionHandler:], which is the holy grail here. If that works, I shall drop my jaw again. On 2013 Apr 23, at 01:47, Mike Abdullah <cocoa...@mikeabdullah.net> wrote: > Receiving a [implicitCancellability equal to] NO *is* going to happen. I agree with Mike. I don't think you're done, Steve. * * * Maybe the confusion is that we are not distinguishing between • Lion Autosave • Tiger Autosave • Some home-made Autosave which Steve's forebears have bequeathed to him Choose and implement one, and only one of these. _______________________________________________ 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
