Blur: Don't hardcode dock border-radius #458
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
zeebok
approved these changes
Oct 28, 2025
Contributor
zeebok
left a comment
zeebok
left a comment
There was a problem hiding this comment.
This code looks good but I am not sure what the different nodes are, and how they relate to the dock? Are they all of the parts that make up the rendered dock "window"?
Member
Author
|
@zeebok well basically yes. When Gtk parses widget tree and CSS it creates render noses that are responsible for different kinds of rendering. |
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.
Introduces RenderNodeWalker that walks through all the render nodes on startup and gets correct border radius