Expand DevTools adding test windows

Merged
DA
4mo ago
+193-44

Add new dev tools to open test windows so their behavior and look can be verified at runtime
These specific windows are usually hard to trigger or unsafe to use if you don't want to mess with your configuration.

The progress window has a simulated timer (1m) thats short enough to see change but long enough to get a look at it.

The message box windows are available in all the supported button types and send the result back as a notification - so you can test its behavior.

UI Changes

To make room for all these new test windows I turned DevTools into an expander

Before

image

After

image

(Messsage Box Type Flyout)
image

Summary by cubic

Replaces the DevTools flyout with a structured expander and adds test windows for Report, Progress (cancelable), Plugin Update, and Message Box. Improves discoverability and lets you verify these UIs safely.

Summary of changes

  • Changed: Converted DevTools SettingsCard + flyout into a SettingsExpander with individual SettingsCards; use shared openFolderButton for settings/log/cache folders; welcome button label is now “Open Welcome Window” (card header still “Wizard”).
  • Added: Buttons to open test Report, Progress (async, ~1 min, cancelable), Plugin Update, and Message Box windows; Message Box includes a flyout for OK, OK/Cancel, Yes/No, Yes/No/Cancel and posts the result as a notification; new localization keys for these labels and openFolderButton.
  • Removed: DevTools flyout and its grouped actions.
  • Memory impact: Minimal; windows are created on demand and disposed on close; progress demo has small, temporary allocations.
  • Security risks: None; all actions are local UI only with no new I/O or network work.
  • Unit tests: None (UI-only changes).

Release Note
About > DevTools now uses an expander with clear actions and adds test windows for reports, progress, plugin updates, and message boxes.