Uploaded image for project: 'Picard'
  1. Picard
  2. PICARD-2334

Have script editor consistently save to configuration

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Normal Normal
    • 2.7.0b3
    • 2.7.0b2
    • Scripting, User Interface
    • None

      Further to the discussion on PICARD-2330 and IRC, there is some confusion when saving scripts in the script editor because the changes are saved as pending edits requiring clicking "Make It So!" if the Options... dialog is open, but are saved directly to the configuration settings if the Options... dialog is not open.  Also having all new scripts created with the same name is inconvenient.  There is also a bug that could display the "unsaved edits" warning incorrectly after changes have been made to a script's metadata.

      For the sake of consistency, the proposal is to always have the script editor "Save" action write the changes directly to the configuration settings, without requiring the "Make It So!" action if the Options... dialog is open.  This would only apply to the file naming scripts and selected file naming script, and would not change the way that all other settings are saved.

            rdswift Bob Swift
            rdswift Bob Swift
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:

                Version Package
                2.7.0b3