Docs say: "Use this method if your code receives paths as C strings from system routines."
Is that the case? If you're just building this string yourself, you can do so directly using NSString methods and this method isn't needed. However, NSURL is the up-and-coming way to represent paths anyway. --Graham On 26/10/2010, at 10:29 PM, G S wrote: > Hi all. I'm giving this function what appears to be a perfectly good path: > > /Users/me/Library/Application Support/iPhone > Simulator/4.2/Applications/58BD5465-FD47-49E3-83AC-242961559F48/Library/Caches/4320_th.jpg > > and it returns nil. If I call UIImage's imageWithContentsOfFile with > the same path, it works. > > Am I overlooking something? I should be using this call to ensure a > legit string, right? Thanks! _______________________________________________ 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 arch...@mail-archive.com
