Skip to content

chore: remove every reference to MultiMonitorTool and SoundVolumeView - #119

Merged
lippdev merged 2 commits into
mainfrom
chore/remove-nirsoft-references
Sep 30, 2026
Merged

lippdev merged 2 commits into
mainfrom
chore/remove-nirsoft-references

Conversation

@lippdev

@lippdev lippdev commented Sep 30, 2026

Copy link
Copy Markdown
Owner

What

Removes every reference to the NirSoft tools (MultiMonitorTool, SoundVolumeView) that the 1.6 own-code backends replaced.

  • AppPaths no longer deletes the old executables from the tools folder at startup.
  • Comments in CoreAudio, NativeDisplays, AudioNaming, DisplayIdentity and ConsoleEngine describe the formats ("the format 1.5 saved") instead of naming the tool. The formats do not change, so settings and backups made by 1.5 keep working.
  • Two test names that cited the tools are renamed; docs/TESTING.md drops the check that the tools folder is cleaned.

Heads-up

  • Anyone updating straight from 1.5 (skipping alpha.2) keeps the two old executables in their tools folder until they delete them by hand. The changelog says so. If that is not acceptable (they are flagged by some antivirus), the cleanup can stay as a name-agnostic or installer step instead.
  • Kept on purpose: the released changelog sections (history of what those versions did) and THIRD_PARTY_NOTICES.md (the notice for the 1.5 releases that did ship the tools).

Verification

Built on Windows locally (Debug x64, 0 errors); dotnet test passes (151). git grep finds no mention outside the two files above. Independent of the other open PRs (base main); the changelog line may need a trivial rebase.

🤖 Generated with Claude Code

1.6 controls displays and audio with Windows' own APIs and bundles none of
the NirSoft tools, but the code, comments, tests and docs still named them.

- AppPaths no longer deletes the old tools from the tools folder at startup.
- Comments in CoreAudio, NativeDisplays, AudioNaming, DisplayIdentity and
  ConsoleEngine now say what the formats are ("the format 1.5 saved") instead
  of naming the tool that used to write them. The formats themselves do not
  change, so settings and backups made by 1.5 keep working.
- Two test names that cited the tools are renamed; docs/TESTING.md drops the
  check that the tools folder is cleaned.

Kept on purpose: the released changelog sections (they record what those
versions did) and THIRD_PARTY_NOTICES.md (the notice for the 1.5 releases that
did ship the tools).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes This review covers the removal of NirSoft-specific references and the associated legacy-file cleanup behavior.

  • Code and test wording Rephrases comments and test names to describe the formats saved by version 1.5 without naming the former tools.
  • Legacy-file cleanup Removes startup deletion of the old executables; the changelog documents that direct 1.5 upgraders retain them until manual removal.
  • Manual testing docs Removes checks that depended on the old tool names and cleanup behavior.

Pullfrog  | View workflow run | Using GPT Luna | 𝕏

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes This review covers the merge from main since the prior Pullfrog review.

  • Package-cleanup note Added the note that only rtss-cli is embedded to both changelogs, clarifying why leftover NirSoft executables are no longer included in the package.

Pullfrog  | View workflow run | Using GPT Luna | 𝕏

@lippdev
lippdev merged commit 95a3168 into main Sep 30, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant