Repository navigation
Fix saving multiple page settings changes - #168
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
2 participants
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.
Changing several values in Page Properties or Page Numbers only saved the first changed value. Replace short-circuiting
||with Booleanorso every update runs while preserving the result indicating whether anything changed.Add regression coverage in SettingsChangeTest using the existing BBTestRunner/SWTBot approach. It changes multiple values through both dialogs, clicks OK, and checks the engine and document settings.
Validation:
.\mvnw.cmd packagepasses with 1,025 enabled tests.Note: Codex was used to help identify this bug. It appears it has been around since end of 2025.
Fixes #167