Re: NSDocument save incremental file package in-place
Re: NSDocument save incremental file package in-place
- Subject: Re: NSDocument save incremental file package in-place
- From: Quincey Morris <email@hidden>
- Date: Sat, 01 Mar 2014 15:06:35 -0800
On Mar 1, 2014, at 14:53 , Mike Abdullah <email@hidden> wrote:
> It is -[NSFileWrapper writeToURL:options:originalContentsURL:error:] which has the feature of writing out hard links for efficiency. But it only does it if requested, by passing a suitable URL as the original contents URL. It is my suspicion that NSDocument does not do this for you. You could set a breakpoint to test this.
I’ve never used this, but I *have* seen documents use hard linking anyway (though, on reflection, that might have been UIDocument, not NSDocument — I’m not sure now).
Your comment makes me wonder if the optimization only happens in certain NSDocument configurations — specifically, it might be necessary to opt into one of the newer NSDocument behaviors, such as the latest style of autosaving.
_______________________________________________
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