Wisp 2.5.3: fix first-time HUD monitor placement - #99
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I fixed a startup path that saved the HUD's temporary monitor before Wisp had identified Forza's window. A HUD without a saved placement now waits for the existing game detection, moves to that monitor without activating a window, and saves its position. Saved layouts and manual placements are preserved. Reset HUD positions also targets the last detected game window, providing a recovery action for existing wrong-screen layouts.
This hotfix updates the app, updater, installer and release history to 2.5.3. It is based directly on public 2.5.2 and contains no private Clips changes.
Validation: Release build passed with zero warnings/errors; 174 focused startup/settings/version/installer-contract tests passed; hidden-window regressions passed across the available monitors for all HUD layouts and both native gauge modes, covering invalid handles, deferred persistence, edit mode, switching to an unsaved style without overwriting the previous style, saved/manual positions, reset recovery and unchanged foreground focus. Additional G-force regressions verify that an active saved position is preserved while unrelated monitor history does not block default placement. Repository policy, release content and changed-file formatting checks passed. The new placement fixture is also included in the full WPF CI checks. No live gameplay test was performed; required CI and installer lifecycle checks remain the publication gates.