The documentation sounds more like it's a convenience method for checking the Unix permissions for deleting the file rather than the HFS locked setting. If you want to consider another non-HFS-aware issue in NSFileManager, the file size info you get from the relevant message only returns the size of a file's datafork, not its resource fork or any other theoretical forks a file may have. For those who believe no one uses resource forks, just look at Safari's in-progress downloads and Finder clippings.
On 04/14/2011 11:26 AM, "Laurent Daudelin" <[email protected]> wrote: >Is it normal that NSFileManager's isDeletableFileAtPath: returns YES for >a locked file? Based on the result it returns, when I try to send it a >removeItemAtPath:error:, it fails and the error localized description is >'³This is a test.docx² couldn¹t be removed because you don¹t have >permission to access it.'. That seems wrong to me. First, >isDeletableFileAtPath: shouldn't return YES for a locked file. > _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
