https://bugs.kde.org/show_bug.cgi?id=490777
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
--- Comment #5 from Nate Graham <n...@kde.org> ---
Sounds like 32" diagonal, which means 69 DPI. Which means the
automatically-calculated scale factor should actually be 75%, not 300%!
I see that you found the DPI that GTK calculated was 294912. Which is, um,
quite a bit more than 69. If you plug that into our scale calculator, it spits
out a scale factor of 307,200%. Which is, um, far too high. So our algorithm
notices this and caps it to 300%, the maximum value.
The fact that both GTK and Qt get the wrong DPI means that your monitor is
reporting the wrong physical size, which causes both toolkits to mis-calculate
its DPI, and than that garbage value gets fed into the scale calculator.
It appears that the screen is reporting itself as having a 0.2mm diagonal
measurement. So now I see why this happens: it doesn't trigger the special code
to detect dumb screens that triggers if the width or height is zero; it's
cleverly reporting itself as slightly larger than zero, but still not a sane
size.
I think we can adjust this check to also check for slightly-higher-than-zero
dimensions that are nonetheless too small to be usable.
--
You are receiving this mail because:
You are watching all bug changes.
