WD Wireless Tools v2.246.8

Launcher: the Windows Terminal tab now opens reliably, and a failure no longer closes the launcher silently

Suite 2.246.8. Tool versions are unchanged.

What changed

Start WD Wireless Tools (Start WD Wireless Tools.bat, Windows)

• The launcher joins an open Windows Terminal window, or opens a new one when none is open. It checks whether Windows Terminal is running first. Previously it always asked for "the most recent window", and after a Windows Terminal window had been closed that request could be accepted without opening anything, so the launcher's own window closed and the app never started.
• The launcher confirms the tab opened. The new tab reports back as soon as it starts. If nothing reports within 15 seconds, the other window choice is tried once, and if that also fails the launcher runs in the window it was started from and prints why. It no longer closes its window on the strength of a tab that never appeared.
• A restart from inside the app uses the same check, so a restart that cannot open its tab falls back to the previous restart behaviour instead of leaving no app running.

The "Open in a Windows Terminal tab" option under Settings, General is unchanged. When it is off, or Windows Terminal is not installed, the launcher runs in its own window as before.

Verified

• A double-click through Explorer was run in both cases: with no Windows Terminal running (a new window opened and the app answered on its port) and with one already open (the existing window was reused, with a single Windows Terminal process afterwards).
• New tests cover the window choice, the confirmation, both fallbacks, the timeout, a stale confirmation left by an earlier run, and the batch file's report from inside the tab. Each fails when the corresponding behaviour is removed.
• The full suite passes.

Files changed

• tools/terminal_tab.py
• Start WD Wireless Tools.bat
• tests/test_terminal_tab.py
• tests/test_launchers_check_dependency_versions.py
• web/assets/versions.json
• README.md