Recapture: fix erroneous maximizing of windows #504
Merged
Conversation
This file contains 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
During a recapture of windows (such as when restarting fvwm3), if a window had been previous maximized (but is no longer), then fvwm3 would think that window should still be maximized. This is because of a missing check to see if the window needs to be maximized. Fixes #143
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
During a recapture of windows (such as when restarting fvwm3), if a
window had been previous maximized (but is no longer), then fvwm3 would
think that window should still be maximized. This is because of a
missing check to see if the window needs to be maximized.
Fixes #143