Re: Finding out that a volume is going away before it does
Re: Finding out that a volume is going away before it does
- Subject: Re: Finding out that a volume is going away before it does
- From: Francis Devereux <email@hidden>
- Date: Tue, 28 Oct 2008 13:40:31 +0000
On 28 Oct 2008, at 05:26, Chris Suter wrote:
On Tue, Oct 28, 2008 at 1:50 AM, Francis Devereux
<email@hidden> wrote:
My code works on 10.4 8A428 PPC (after I changed mainRunLoop to
currentRunLoop), but this probably isn't much help to you because
DiskArbitration.framework is private on 10.3.
You can use it fine on 10.3. As far as I know, there was no change to
the interface between 10.3 and 10.4 (or none that will bother you).
You just need to make sure you link to the framework in
/System/Library/PrivateFrameworks rather than
/System/Library/Frameworks.
NSWorkspace will ultimately be using DiskArbitration; there's no other
way for it to work.
You're right, I updated my test project to use install_name_tool to
change the reference to /System/Library/Frameworks/
DiskArbitration.framework to /System/Library/PrivateFrameworks/
DiskArbitration.framework and it works on 10.3.9. Updated version at http://www.devrx.org/software/osx/DiskArbitrationTest.zip
in case anyone wants to have a look.
Francis
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden