But hard-coding a path is a bad idea. Better to have the user select the folder once, then store the string returned from "GetSaveInfo" somewhere like a prefs file. On the next run, you can recreate the destination from that string.

If you download the MacOSLib package, there is true alias handling code and plist code within that will not only let you save an alias, but will mount the volume for you when you try to resolve it.

But hard-coding a path is a bad idea. Better to have the user select the folder once, then store the string returned from "GetSaveInfo" somewhere like a prefs file. On the next run, you can recreate the destination from that string.

If you download the MacOSLib package, there is true alias handling code and plist code within that will not only let you save an alias, but will mount the volume for you when you try to resolve it.

In the macoslib folder, look for the FileManager module and the FSAliasRecord within. For PLists, there are a number of ways, but the easiest is to use MacPListBrowser in the Additional Modules. EXCEPT, in testing, I found there is problem when retrieving FolderItems that no longer exist, so I will be posting an update to MacOSLib later. Once I do, you can do something like this:

In the macoslib folder, look for the FileManager module and the FSAliasRecord within. For PLists, there are a number of ways, but the easiest is to use MacPListBrowser in the Additional Modules. EXCEPT, in testing, I found there is problem when retrieving FolderItems that no longer exist, so I will be posting an update to MacOSLib later. Once I do, you can do something like this: