diff options
| author | Ken Moore <ken@ixsystems.com> | 2017-05-03 09:30:19 -0400 |
|---|---|---|
| committer | Ken Moore <ken@ixsystems.com> | 2017-05-03 09:30:19 -0400 |
| commit | bd5105d652b0bea53da267297bfb5500c57a7e52 (patch) | |
| tree | e832e88ce8e9332b81316ee1b03a448c9eea178b /icon-theme/material-design-dark/applications/google-play.svg | |
| parent | Merge branch 'master' of github.com:trueos/lumina (diff) | |
| download | lumina-bd5105d652b0bea53da267297bfb5500c57a7e52.tar.gz lumina-bd5105d652b0bea53da267297bfb5500c57a7e52.tar.bz2 lumina-bd5105d652b0bea53da267297bfb5500c57a7e52.zip | |
Clean up how the high-DPI settings for lumina are detected/enabled.
Now whenever a screen is added/changed it will print out the physical/logical DPI values into the log, and if a logicalDPI (X or Y) is greater than 110 it will enabled the Qt5 auto-scale functionality.
Note: My 1080p laptop monitor has a logical DPI of ~96, but a physical DPI of ~150 and the Qt5 auto-scale stuff is based on physical DPI (so things got massive on a normal-res screen). I am leaving the DPI print-out in the logs for now so that if we run into any other monitors where the logicalDPI>110 rule is invalid we can view/tweak the rule really easily.
Diffstat (limited to 'icon-theme/material-design-dark/applications/google-play.svg')
0 files changed, 0 insertions, 0 deletions