Fix some VisualShader features for high DPI displays/custom UI scales #93903
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
|
Works A1 on my Macbook Pro. 
|
adamscott
approved these changes
Jul 3, 2024
Geometror
force-pushed
the
vs-fix-frame-edscale
branch
from
2c0c5fc to
b871794
Compare
Geometror
changed the title
GraphFrame autoshrink with high DPI displays/custom UI scales
|
Small update: Now the reroute node looks identical regardless of the UI scale and uses AA. |
|
Thanks! |
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.
Changes:
GraphFrameautoshrink not taking titlebar height into account and adjusts the VisualShader theme.A new unexposed getter getter for the titlebar height is added. (As
get_titlebar_hboxis notconst)Before (200% editor scale):
After (200% editor scale);