It seems that PWP remembers the last saved script only when it was saved by the dialog Save Current Workspace.
1. close PWP and confirm to save the current workspace when asked by the dialog Save Current Workspace?
When you then open PWP you get (if set in Preferences) the dialog Restore Previous workspace? with three options : Don't restore, Restore the last saved.., and Ask for workspace to restore.
2. Save the current workspace using Script sub menu or Close all images commands, do some work (not worth saving), close PWP and dismiss saving workspace when asked by the dialog.
When you then open PWP you get the dialog with only two options : Don't restore, and Ask for workspace to restore.
Two more comments:
If you load another script, then on closing you are rightly asked to save this script name.
If you open an image, then on closing you are rightly asked to save the system generated name.
If PWP remembered the last saved workspace no matter when the script was saved, only one dialog (the one with three options) would be enough on starting PWP and the last saved script would always be among the options.
Unless there is something behind that I am not aware of.
Saving workspace scripts revisited
Moderator: jsachs
Re: Saving workspace scripts revisited
There are two different models of how this feature works, and maybe it was a mistake to try to combine them.
1) As you suggest, just keep track of the last script saved and have a command to reload the last script saved. Give the user the option to save the current workspace on exit or Close All Images.
2) On exit, save everything and optionally restore it all on the next startup. This is the idea behind saving with the current date and time.
Using the current scheme, if you save the current workspace on exit, it will be one of the options the next time you start up. Or, if you save with the current date and time, that will be the option to restore. The scenario I am concerned about is that you load a workspace script, make a few changes and exit without saving the changes. If you just remember the name of the last workspace saved, on the next startup you lose the changes you made.
Maybe these two ideas should be totally separate and you should be able to set preferences to automatically save the current workspace by date and time on exit and, at the same time, keep track of the last script opened or saved. On startup, you would then get both options to reload.
1) As you suggest, just keep track of the last script saved and have a command to reload the last script saved. Give the user the option to save the current workspace on exit or Close All Images.
2) On exit, save everything and optionally restore it all on the next startup. This is the idea behind saving with the current date and time.
Using the current scheme, if you save the current workspace on exit, it will be one of the options the next time you start up. Or, if you save with the current date and time, that will be the option to restore. The scenario I am concerned about is that you load a workspace script, make a few changes and exit without saving the changes. If you just remember the name of the last workspace saved, on the next startup you lose the changes you made.
Maybe these two ideas should be totally separate and you should be able to set preferences to automatically save the current workspace by date and time on exit and, at the same time, keep track of the last script opened or saved. On startup, you would then get both options to reload.
Jonathan Sachs
Digital Light & Color
Digital Light & Color