FROM : Chris Suter
DATE : Sun Jul 02 03:47:12 2006
On 02/07/2006, at 11:39 AM, Dean Snyder wrote:
> I wrote at 3:57 PM on Saturday, July 1, 2006:
>
>> So you're saying that there is no new file creation going on with
>> NSFileManager movePath? Then why do both the created and modified
>> dates
>> of the just "moved" file equal the time of "moving" and not, for
>> example, the "real" created time?
>
> I need to correct this.
>
> If I change the contents of the file and save it (using NSTextView
> writeRTFDToFile), but do not rename/move the file, then both the
> creation date and the modification date are changed to reflect the
> time
> the file was saved. That is clearly wrong behavior - only the
> modification date should be changed.
What effect does the atomically flag have on it? If you see this
behaviour with it set to YES, it wouldn't surprise me, but it
shouldn't be the case with it set to NO.
DATE : Sun Jul 02 03:47:12 2006
On 02/07/2006, at 11:39 AM, Dean Snyder wrote:
> I wrote at 3:57 PM on Saturday, July 1, 2006:
>
>> So you're saying that there is no new file creation going on with
>> NSFileManager movePath? Then why do both the created and modified
>> dates
>> of the just "moved" file equal the time of "moving" and not, for
>> example, the "real" created time?
>
> I need to correct this.
>
> If I change the contents of the file and save it (using NSTextView
> writeRTFDToFile), but do not rename/move the file, then both the
> creation date and the modification date are changed to reflect the
> time
> the file was saved. That is clearly wrong behavior - only the
> modification date should be changed.
What effect does the atomically flag have on it? If you see this
behaviour with it set to YES, it wouldn't surprise me, but it
shouldn't be the case with it set to NO.






Cocoa mail archive

