File naming script UI is overly complex and duplicated

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Normal
    • 3.0.0b5
    • Affects Version/s: None
    • Component/s: User Interface
    • None

      File naming script management is split across two places:

      • The Options dialog has a script selector combo box, example previews, and an "Edit" button
      • The main menu has the same script list as a submenu, plus an "Open editor" action

      This causes several issues:

      1. Confusing UX: Users don't know which is the "real" place to manage scripts. The term "Selected" is ambiguous — selected in the combo box, or actually used for renaming?
      2. Complex sync logic: Opening the script editor from Options vs from the menu requires different signal wiring. Opening Options while the editor is open requires disconnecting/reconnecting signals to avoid conflicts. This is fragile and has caused bugs.
      3. Code duplication: ~500 lines of sync code, dual-parent logic (is_options_ui() / is_main_ui()), and a signal disconnect dance exist solely to keep both UIs in sync.
      4. Rename/move toggles appear in both the Options dialog page and the main menu, adding redundancy without value.

      Proposed solution:

      Single source of truth: scripts are managed exclusively from the main menu (Options › File naming scripts), with the Options dialog page limited to rarely-changed configuration (destination directory, file patterns, compatibility settings).

            Assignee:
            Zas
            Reporter:
            Zas
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:

                Version Package
                3.0.0b5