Anybody else come across this? I suppose I could check the path for
alias folders, and resolve them, but this seems like extra work.
Surely the CoreData loading functions would traverse the paths
correctly?
This has nothing to do with Core Data. Finder aliases are not
resolved automatically in the same way that symbolic links are; they
need to be resolved manually using the Carbon File Manager. This is
not normally a problem as only manually-typed paths are likely to
contain elements that are Finder aliases; paths returned by
NSOpenPanel or NSSavePanel won't.
-- Chris
_______________________________________________
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
