Re: differences between NSWorkspace unmountAndEjectDeviceAtURL and unmountAndEjectDeviceAtPath
Re: differences between NSWorkspace unmountAndEjectDeviceAtURL and unmountAndEjectDeviceAtPath
- Subject: Re: differences between NSWorkspace unmountAndEjectDeviceAtURL and unmountAndEjectDeviceAtPath
- From: Jim O'Connor <email@hidden>
- Date: Mon, 3 May 2010 10:37:46 -0800
The system call works.
As does the call to FSEjectVolumeSync(), which surprised me, since I thought that if the NSWorkspace call failed then I must be missing some step.
Thanks,
Jim
On May 3, 2010, at 7:13 AM, James Bucanek wrote:
> Jim O'Connor <mailto:email@hidden> wrote (Sunday, May 2, 2010 11:27 PM -0800):
>
>> My alternative is to call system with hdiutil detach, which is ugly.
>
> I would have thought that the alternative would be to get the volume's FSVolumeRefNum and simply call FSEjectVolumeSync(), which is ultimately what (I believe) NSWorkspace does.
>
> This would require about eight lines of code, and really isn't that ugly.
>
> --
> James Bucanek
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden