Question

I just noticed something weird in my app.

I have a “save” button that triggers this function:

 var saveFile:File = File.desktopDirectory.resolvePath(nameOfProject+".uct");
 saveFile.browseForSave("Save as");
 saveFile.addEventListener(Event.SELECT, saveFileToSystem);

When clicked, it display the “browse for save” window with a suggested name file.
Now I’ve noticed that when exporting, installing and running the app, when I click the button for the first time everything it’s ok, but when I clicked again the location looks like this:

The “where” field is the same file….? And even if I click save, it doesn’t save. The strange stuff is that this is not happening while testing my app in Flash Builder.
Any hint?

Answer 1

I did the workaround above, and it seems to do the trick. Code is something like this:

var saveFile:File = File.documentsDirectory.resolvePath("output.file");
var tempMovedAway:File = File.applicationStorageDirectory.resolvePath("temp.temp");
currentFileRenamedForAirBug = picker.clone();
currentFileRenamedForAirBug.moveTo(tempMovedAway), true);
saveFile.addEventListener(Event.SELECT, function():void {
        tempMovedAway.deleteFile();
    } );
saveFile.addEventListener(Event.CANCEL, function():void {
        tempMovedAway.moveTo(currentFileRenamedForAirBug);
    });
saveFile.browseForSave("save file"); 
// MUST be sure to call saveFile.browseForSave, or you risk losing an existing file.

You can wrap this lot in checks for the Air runtime (NativeApplication.nativeApplication.runtimeVersion) and Mac-only, to avoid doing this any more than necessary.

Also, if your file save code could rely on making changes to an existing file (rather than creating an entirely new one), you’ll need to tweak this a bit.