wxWidgets

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

It doesn't look like this one is going to be applied so it's probably
useless to leave it open...

Logged In: YES
user_id=81467

Hi Ryan

I will probably completely privatize the method to make
sure it is not used anymore, and I'll add the assert, to
make sure things don't get unnoticed. Is there a call you
needed an FSSpec for which doesn't have another API ?

Best,

Stefan

Logged In: YES
user_id=304442

The problem didn't happen with any wx code, but in my user code.

If you don't want to use the patch, could you at least:
a) put a #warning in wxMacFilename2FSSpec that says
FSSpecs are depreciated
b) Do some error checking of the result from
wxMacPathToFSRef (which does return the OSStatus) and
throw up a wxASSERT_MSG (or wxLogError()...) so
unwary travllers are _told_ that the operation
didn't work (instead of wondering why their FSSpec
is invalid...)

Logged In: YES
user_id=81467

Hi Ryan

thanks for your patch, but actually as FSSpec are
deprecated, we rather have to get rid of them completely.
wxMacFilename2FSSpec should not be used anywhere right now
in wx in any place where the file does not exist, where did
this problem happen ?
wx OS X builds IIRC currently use them only in QT,
drag&drop and NavigationServices. As FSSpecs are not
unicode aware, they should not be used for creating new
files.
What was the piece of code at the caller side that lead to
the problem ?

Thanks,

Stefan