Re: Why is NSString->FSRef so hard?
Re: Why is NSString->FSRef so hard?
- Subject: Re: Why is NSString->FSRef so hard?
- From: Erg Consultant <email@hidden>
- Date: Mon, 27 Apr 2009 21:26:03 -0700 (PDT)
One other thing I should mention - the mangled char in question is the tm symbol (option-2). In its string form, the debugger shows it as the tm char.
But when I convert the string to an NSURL using fileURLWithPath, and then do a CFShow, the tm is converted to *three* hex chars:
™
Are NSURL and CFURL not toll-free bridged?
Erg
________________________________
From: Sean McBride <email@hidden>
To: Erg Consultant <email@hidden>; email@hidden
Sent: Sunday, April 26, 2009 2:41:20 PM
Subject: Re: Why is NSString->FSRef so hard?
Erg Consultant (email@hidden) on 2009-04-25 7:33 PM said:
>Isn't there some easy way to get an FSRef from an NSString that is a
>path containing special characters?
You can use NDAlias:
<http://github.com/nathanday/ndalias/tree/master>
It provides an NSString category that converts to/from FSRef.
Sean
_______________________________________________
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