Re: NSDocument data-based primitives
Re: NSDocument data-based primitives
- Subject: Re: NSDocument data-based primitives
- From: Ondra Cada <email@hidden>
- Date: Mon, 28 Mar 2005 04:03:33 +0200
On 28.3.2005, at 3:43, Julien Palmas wrote:
Still in my investigations with NSDocument implementation, I've found something a bit strange in the <x-tad-bigger>- (BOOL)writeToFile:(NSString *)fileName ofType:(NSString *)type method.
I expected fileName to be exactly the path in gave in the save panel. But it is actually a path that looks like this:
"/private/tmp/501/TemporaryItems/com.apple.myApp_604_133666110_1/myFile.xxx"
Is that normal ???
</x-tad-bigger>
<x-tad-bigger>
Quite. It is documented somewhere... can't just now recall the exact place (well, NSDocument documentation is the most usual suspect :))
The culprit is that NSDocument tries to be smart and saves atomically by default to remove any possibility of data loss, at the same time keeping aliases pointing to the file, and who knows what else :)
</x-tad-bigger>---
Ondra Čada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden