Why not just call it every time it starts up? I can't imagine the
overhead of the API call is very high.
Devon.
Mitchell Livingston wrote:
How can I call it again if I don't know it moved? Waiting until it fails is a
bit too late in the process. Sure, chances are the app won't move, but why
should it ever fail? Storing it in the library folder is not a real good option.
On Thursday, July 17, 2008, at 12:09AM, "Omar Qazi" <[EMAIL PROTECTED]> wrote:
On Jul 16, 2008, at 8:28 PM, Mitchell Livingston wrote:
But if the app is moved, the string that was previously returned
from the call is no longer valid.
So... call it again. You can do this whenever the user starts your
application, or when the call returns an error saying that it can't
find the file.
You might be worrying about this too much. How often will a user move
your application? If these files don't change you might even consider
copying them to the user's library folder the first time your app is
run.
Omar Qazi
Hello, Galaxy!
1.310.294.1593
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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/dferns%40devonferns.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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]
