chore(appearance): make window gap and active hint size constraint consistent#1667
Open
hojjatabdollahi wants to merge 1 commit into
Open
chore(appearance): make window gap and active hint size constraint consistent#1667hojjatabdollahi wants to merge 1 commit into
hojjatabdollahi wants to merge 1 commit into
Conversation
…nsistent Keep the constraint consistent in both directions: - increasing active_hint may increase gaps (handled in set_active_hint) - decreasing gaps should also decrease active_hint if it would otherwise exceed gaps
adil192
suggested changes
Feb 18, 2026
| let active_hint = self.builder().active_hint; | ||
| if gap < active_hint { | ||
| self.set_active_hint(gap)?; | ||
| } |
There was a problem hiding this comment.
It would be more consistent to move this check into ThemeCustomizer further down this file, since that's where the "Update the gap if it's less than the active hint" check is.
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
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 created a separate PR for this, since I'm not sure if the current design is preferred.]
Keep the constraint consistent in both directions: