Carbon.File.FSSpec currently doesn't accept non-existing pathnames. This can be fixed in a way similar to what EasyDialogs.AskFileForSave uses, I think.
Logged In: YES user_id=6656 This would seem to be a dup of 585923 which is closed, fwiw. I don't understand the comment about EasyDialogs.AskFileForSave.
Logged In: YES user_id=45365 I re-submitted this by popular demand. And, indeed, the logic could be similar to what AskFileForSave does (even though that is not 100% correct), but this code has to be in C:-(
Logged In: YES user_id=6656 I know, you posted this after a complaint from me :-) It seems to me that the hacks AskFileForSave perpetrates are going the other way, from FSSpec of absent file to pathname. Can it be done backwards? I guess pain comes from not being able to call os.path.split in C...
Logged In: YES user_id=45365 Sort of. If the user wants an fsspec back you need to construct it. The difficult bit is getting the MacRoman (or whatever the local convention is)/utf-8 handling right. And then there's the 31-char limit for FSSpec filenames, which OSX handles with magic under the hood (but for non-existent files we don't have to worry about this). But: if you're willing to do a 90% fix (say, by requiring ASCII in the last part of the filename): be my guest!
