Re: Why is NSString->FSRef so hard?
Re: Why is NSString->FSRef so hard?
- Subject: Re: Why is NSString->FSRef so hard?
- From: Jean-Daniel Dupas <email@hidden>
- Date: Tue, 28 Apr 2009 18:59:07 +0200
Le 28 avr. 09 à 17:47, Michael Ash a écrit :
On Tue, Apr 28, 2009 at 1:13 AM, Erg Consultant
<email@hidden> wrote:
Apple's doc's specifically say to stay away from using the
"CString" routines which require encodings. So now the encoding
issue goes away. The problem is LSOpenApplication() does not like
the FSRef I pass it which gets created from the path NSString-
>CFURL->FSRef.
They state the opposite. They say to stay away from the ones which do
NOT require encodings. That's because the ones without encodings use
the "system encoding" which is not guaranteed to be anything useful.
The ones with encodings require you to specify them yourself and are
therefore just fine.
And to add a word about your LS issue, it's because to launch an app,
you should create a ref on the bundle, not on the executable.
_______________________________________________
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