https://bugs.kde.org/show_bug.cgi?id=429236
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sit...@kde.org
--- Comment #4 from Harald Sitter <sit...@kde.org> ---
I have: output scale=1.5 in wayland. I switch to x11 globalscale=1. What I then
see is that
systemsettings(36246)/(default) KScreen::Output::geometry: logicalsize
QSize(2560, 1440) dptr size QSize(3840, 2160)
where logical size /1.5 of the real resolution
systemsettings(36246)/(default) KScreen::Output::logicalSize: scale 1.5
What I believe happens here is that since wayland supports per-screen scaling
the scale is recorded in the backing configs
grep -ri 1.5
control/outputs/af15716759a8cd23110c74dd7f1fb852: "scale": 1.5
control/configs/db639558b75873b5ba72f206a3712a16: "scale": 1.5
but then on x11 per-screen isn't a thing so that's meaningless. BUT the Output
class still reads the value and the KCM still uses the value to get relative
sizing and whatnot. So this may indeed be the other side to the coin that is
bug #433460 but I don't really have sufficient overview of the stack. It occurs
to me that if libkscreen's Output class correctly dealt with scaling behind the
scenes (that is to say: use the global config when in x11 or per-display in
wayland) then everything built on top should work.
--
You are receiving this mail because:
You are watching all bug changes.
