Re: Temporarily disabling autosave
Re: Temporarily disabling autosave
- Subject: Re: Temporarily disabling autosave
- From: Steve Mills <email@hidden>
- Date: Tue, 23 Apr 2013 10:18:02 -0500
On Apr 23, 2013, at 09:19:47, Jerry Krinock <email@hidden> wrote:
> 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.
What do you mean by "not running the show in Lion autosave"? As opposed to 10.8 and later, or 10.6 and earlier? (Please use numbers, as it's easier to remember the order of numbered versions.)
> 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.
Yes, we get this message when running under 10.8.
--
Steve Mills
office: 952-818-3871
home: 952-401-6255
cell: 612-803-6157
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden