https://bugs.kde.org/show_bug.cgi?id=401179
Filipe Azevedo <pas...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #7 from Filipe Azevedo <pas...@gmail.com> ---
Let recap things, because i have the feeling i did not emphasized enough on the
issue being *dual* screens with internal screen being a retina screen and the
external one a full hd screen non retina, under X11.
If you have only a retina screen - the kcm scale feature just work, but break
as soon as you add another screen, simply because it's an all screens scale.
To be honest this *global* scale feature is useless, i still can't understand
how it was accepted.
Note that I do know that wayland can do per screen scale factors, but i don't
care because wayland/nouveau is all but stable on a mac machine.
I did disable my script (command is: xrandr --output DP-2 --scale .5x.5
--output HDMI-0 --pos 1440x0) which is basically downscaling the screen picture
of the retina screen half its size and move the other screen near it so that it
make a contiguous plan.
This script is executed by the user session autostart kcm - and it just do the
job.
The *only* draw back is that the downscale has a lower rendering quality, but
clearly acceptable for what it fix.
So, i the initial request title is somehow wrong - because in reality we may
not speak about the same feature.
kscreen kcm seems to apply a xorg screen scale feature, while i do speak about
xrandr scale property.
I have no idea what kscreen try to do behind the scene (but i really would like
to know the details, even pointing the exact code applying the changes), but
what i need is an out of the box working solution for a retina mac with
external screens plugged.
Hope it help understanding correctly the issue.
--
You are receiving this mail because:
You are watching all bug changes.
