Re: FW: NSFileManager
Re: FW: NSFileManager
- Subject: Re: FW: NSFileManager
- From: Greg Titus <email@hidden>
- Date: Sun, 24 Jun 2001 11:03:57 -0700
On Sunday, June 24, 2001, at 10:40 AM, Aaron Tuller wrote:
an easier way to get to files in your Resources directory is [[NSBundle
mainBundle] resourcePath]
-aaron
At 10:08 AM -0700 6/24/01, Tommy Braas wrote:
I am trying to use NSFileManager to get the current working directory
path from a Cocoa application. I don't want to throw up a file chooser
as I am trying to read a preferences file from within my application
package. Whenever I use the following code the output is "/" when I
run the application by double-clicking.
Aaron is right, but to explain a little more what is happening:
The NSFileManager -currentDirectoryPath method returns the current
working directory that is passed in to the app as part of its
environment when it is started up. This has nothing to do with where the
Application is actually installed. ProjectBuilder explicitly sets this
to the app directory, Finder explicitly sets this to "/", if you started
the app from the command-line, the result from this method would be
whatever directory you were currently in in the shell when you started
the app.
Since you say you are trying to read a preferences file inside your app,
you should use [[NSBundle mainBundle] pathForResource:ofType:], which
will return the correct path inside your application, and also do the
correct thing (look inside language directories) if the file you are
looking for can be localized for different languages.
Hoep this helps,
--Greg