I stopped the app and searched for that file. A file created in this
way will always be created in the current directory. Although this
proves it, it's tedious. I would control your directory by always
using the -changeCurrentDirectoryPath: before any writing or reading.
Much better is to simply do what most people do and never use relative
paths for anything with anything ever.
The only time I would even consider touching these methods is if I was
integrating weird legacy code that relied on the working directory.
For new code I never write anything that uses relative paths.
Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
