Enable Qt's high-DPI scaling on Linux #204
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
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.
Further/extensive testing by someone who actually uses high-DPI monitor has indicated that enabling
AA_EnableHighDpiScaling(via theQT_AUTO_SCREEN_SCALE_FACTORenvironment variable) works and "is a must" on GNOME as well as a number of other desktop environments (including Budgie, Cinnamon, Deepin, KDE, and XFCE). The only exception to this, reportedly, was MATE -- which, I've been told, works/looks better with auto-scaling disabled...Accordingly, this PR enables on auto-scaling for all platforms/environments except for MATE and Qubes-OS (which, as mentioned in the in-code comment, continues to apply inconsistently).
Note that Qt's auto-scaling can still be enabled or disabled by setting the
QT_AUTO_SCREEN_SCALE_FACTORenvironment variable to1or0(respectively), allowing users to override Qt's behavior independently of this change and/or on a per-application basis as desired.