Oooops. It looks like I lied.
Actually, I am using
[[[myFileManager fileSystemAttributesAtPath:[mountedDiskImagePath
stringByDeletingLastPathComponent]
...]
I think it was because sometimes the path included a filename. I am
going to change it to use the full path. I never noticed this problem
until I tried to copy to the root level of a disk, which is not the
normal way this app would be used. Isn't that what QA is for?
(5 minutes later)
That works, I think. I will need to test it some more before I am
certain.
On Oct 28, 2008, at 2:17 PM, Clark Cox wrote:
On Tue, Oct 28, 2008 at 2:15 PM, Paul Archibald <[EMAIL PROTECTED]> wrote:
This is pretty obscure, I think.
My app makes files which can be quite large. It also allows the
user to
distribute copies of those files to various locations. So, to test
this I
have tried creating and mounting a disk image which I tried making
a copy
to.
The problem is that it seems I cannot check the actual available
space on
that mounted disk image. What I get instead is the available space
on the
disk where the image lives.
I am using [[myFileManager
fileSystemAttributesAtPath:mountedDiskImagePath]
objectForKey:NSFileSystemFreeSize];
Is mountedDiskImagePath the path to the disk image itself, or to the
place at which the image is mounted?
--
Clark S. Cox III
[EMAIL PROTECTED]
_______________________________________________
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]
