problem creating a file (rather long)

hello,

I write an application (carbon), both for OS9 and OS X. By the way, I'm
still looking for an IDE
able to produce the two executables on a single plateform. I'm currently
working alternatively with
ProjectBuilder and CodeWarrior to do that. But it is not my main problem
:-(((

My app have to propose three choices for locating the destination folder
for the new file:
the desktop (it works), the same location as the source (it works), and
a custom destination
stored in the prefs, after being located but the user: doesn't work.

I have tried this way:
In the prefs dialog, I call "NavCreateChooseFolderDialog" to allow the
user to select his
destination folder. First little problem: this dialog displays itself
with an "open" label for the
accept button, instead of the "choose" I want, and no "Open" button to
allow the user to navigate ???
I have select options by the following code:

osError = NavGetDefaultDialogCreationOptions (&dialogOptions);
dialogOptions.optionFlags = kNavDefaultNavDlogOptions; /*
defaults options*/
dialogOptions.optionFlags += kNavAllFilesInPopup; /* allows "all
documents"*/
dialogOptions.optionFlags -= kNavAllowStationery; /* no
"Stationery"*/
dialogOptions.optionFlags -= kNavAllowPreviews; /* no
"Previews"*/
dialogOptions.optionFlags -= kNavDontAddRecents; /* don't add
Recents;*/
dialogOptions.optionFlags -= kNavAllowMultipleFiles; /* unique
selection;*/

Then I call :
NavCreateChooseFolderDialog (&dialogOptions,

gChooseFolderEventFunctionUPP,
NULL,
NULL,

&gModalToApplicationNavDialogRef)
and, in the event function, I have:
switch (navUserAction)
{
case kNavUserActionChoose:
if ((osError = AEGetNthPtr
(&(navReplyStruc.selection),
1,
typeFSS,
&keyWord,
&typeCode,
&volatileFSSpec,
sizeof(FSSpec),
&actualSize)) ==
noErr) { ....

So, I hope to have the FSSpec of the directory where I should put my
file...
To be clean, I store only the path of this directory in my prefs. I have
this path
using a FSRef.

When I try to create my file, I first convert the path into a FSRef of
the directory:
osError = FSMakeFSSpec (0,
0,
currentPrefs.destPath,
&localeFSSpec);


Then, I use this FSSpec's vRefNum and parID, added to my fileName, to
create the
good FSSpec.

osError = FSMakeFSSpec (localeFSSpec.vRefNum,
localeFSSpec.parID,
theOutputFSSpecPtr->name,
theOutputFSSpecPtr);

The file is created, under OSX, in the application's package !!!!

I'm sure that I have follow the simpliest path, and ready to change my
options.
But I need help.

Thanks for any argumented suggestion.

In article <403DA940.5630FC2D.DeleteThis@supelec.frNOSPAM>,
henri delebecque <henri.delebecque.DeleteThis@supelec.frNOSPAM> wrote:

 > I write an application (carbon), both for OS9 and OS X. By the way, I'm still
 > looking for an IDE able to produce the two executables on a single plateform.
 > I'm currently working alternatively with ProjectBuilder and CodeWarrior to do
 > that. But it is not my main problem

CodeWarrior works fine for both Mac OS 9 and Mac OS X.

 > I have tried this way: In the prefs dialog, I call
 > "NavCreateChooseFolderDialog" to allow the user to select his destination
 > folder. First little problem: this dialog displays itself with an "open"
 > label for the accept button, instead of the "choose" I want, and no "Open"
 > button to allow the user to navigate ???

I believe this mislabeling is a known bug in Mac OS X 10.3 and will be fixed.
The "Open" button is not used for folder navigation at all.

 > To be clean, I store only the path of this directory in my prefs. I have
 > this path using a FSRef.

You should probably be saving an alias, not a path.

 > When I try to create my file, I first convert the path into a FSRef of
 > the directory:
 > osError = FSMakeFSSpec (0,
 > 0,
 > currentPrefs.destPath,
 > &localeFSSpec);

This is wrong. FSMakeFSSpec takes a path, but it's a :-separated path, not a
/-separated path, and it's limited to 255 characters, so you should just not use
that functionality for your purpose. Instead, look at FSPathMakeRef and
FSRefMakePath.

 > Then, I use this FSSpec's vRefNum and parID, added to my fileName, to
 > create the good FSSpec.

After you get the FSRef as I desribed above, you should use FSCreateFileUnicode
to create the file. That will allow you to use long filenames. However, if you
insist on sticking to the outdates FSSpec APIs, call
FSGetCatalogInfo to convert the parent FSRef to an FSSpec, and then use
FSMakeFSSpec to create the FSSpec for the file itself.

hth

meeroh

--
If this message helped you, consider buying an item
from my wish list: <http://web.meeroh.org/wishlist><!-- ~MESSAGE_AFTER~ -->