Re: FSCopyObjectAsync: useless and crippled
Re: FSCopyObjectAsync: useless and crippled
- Subject: Re: FSCopyObjectAsync: useless and crippled
- From: "Louis C. Sacha" <email@hidden>
- Date: Mon, 16 May 2005 22:03:50 -0700
Hello...
If you haven't already, you could (should?) add a feature to your
main application with the options to quit or restart the helper
process. It's simple to implement that sort of thing with distributed
notifications, and it will allow your users to quit the running
background process before (or after) updating to a new version.
Cocoa provides NSDistributedNotificationCenter as a part of the
Foundation framework, and distributed notifications are also
supported in CoreFoundation through CFNotificationCenter for Carbon
apps and low level tools.
If you want to do drag and drop install, there isn't a clean solution
to avoid the replace issue. Even putting the helper somewhere else
has [OT] issues of it's own. The least problematic solution for a
drag and drop install is for your users to manually drag the old app
bundle (which also contains your helper app) to the trash first, or
manually quit the background helper app first (or before they empty
the trash if they drag the old app to trash themselves).
Hope that helps,
Louis
rm -rf TextEdit.app does not constitute a drag and drop
installation. There is no way I'd ever expect an end user to use a
command line like that.
It's not the launching from the Finder that is the problem, but the
replacement with the Finder.
Mark Munz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden