Wouldn't it be nice to have a 'Save Script As..." function?

[Manu Chao]

Originally Posted by dnanian

No. The whole idea of including a base script (as opposed to modifying an existing one) is that changes we make in future versions are automatically reflected in the included versions.

Maybe then just make the UI clearer. Right now it looks as if one could modify one of the base script (Edit Script), but since one cannot save it under a different name one would loose access to the original base script. In other words, if the base scripts are not supposed to be edited (so you can update them), they should not be presented in a way that makes them seem editable.

In other applications, when you select to create a new script, one is given a list of options to choose from (either via a dialogue box with several 'buttons' or via a dropdown menu, the equivalent of your base scripts). In SD, the hierarchy between 'scripts' and 'script commands' is rather unclear to me. It seems everything is a script and that hierarchy does not matter. But what happens if script A says exclude folder X and script B (set to include script A) says include folder X?

Furthermore, it seems settings and scripts are saved independently from each other (with scheduled copies at least being based on scripts). And do settings actually save the options? Or what else do they save? So, what happens if you have a scheduled copy that runs fine on its own is using a smart copy and then for a different operation you change from smart copy to erase & copy? Will this affect the scheduled copy? Or does the scheduled copy include the settings that were active when it was created?