Hi, Luke.

Auto-save is set up on a per-"named configuration" basis. So if you have multiple named configurations, they can each have their own auto-save settings (you might have a set of targets you always want to save, and another set you don't really care about - disposable one-off targets, for example).

This extension uses the masking of auto-saves because there's already a user interface there for it. There are certainly other ways to do this. If you open the .ppx file, you can "tweak" this a bit yourself. The interesting stuff happens starting on line 55 - you can see how the auto-save status is checked and then the mask is set. The filename is calculated from the mask setting (that's really what we're using here - we need to know what mask to use, so we use the existing set).

If you want some different behavior, there are a few possibilities, we just need to figure out how it *should* work. If you always want it saved to the same directories, with the same mask, that logic could very easily be inserted into the script. If you want it to prompt you, using a default (maybe the default from the last time), again, that can be easily inserted. One of the great things about these extensions is that they can be evolved over time, based on requirements, and once things get nailed down enough, we can incorporate them into the application.

For the current implementation, if you set your auto-save interval to something like "30 days", then you won't have to worry about auto-save actually happening, but this script will still work.

We'll probably get a "save data with workspace" option in a future release, but there are some complexities with that which made us *not* include it yet.

- Pete