D12405: [WIP] Per-screen scale factors on X11 using QT_SCREEN_SCALE_FACTORS

[Nathaniel Graham]

ngraham added a comment.


  We're past 5.14 and into 5.15 territory now. Does this deserve another look?
  
  My personal opinion is that it's not wise to under-invest in the X11 code while Wayland is still very much a work in progress. I get that it's frustrating to work on code that you know is going to be obsolete, but the time before that happens may be longer than we all think: we've been promising Wayland for years and it's still not at feature parity with X11, and on top of that there are many showstopping user-visible Wayland-specific bugs. I know for me personally it's unusable due to https://bugs.kde.org/show_bug.cgi?id=387156 and https://bugs.kde.org/show_bug.cgi?id=387721 and https://bugs.kde.org/show_bug.cgi?id=384637 and https://bugreports.qt.io/browse/QTBUG-51640 and https://community.kde.org/Plasma/Wayland_Showstoppers#No_remote_support. I would love to use our Wayland session, but because of those issues, I just can't. I suspect a lot of users are in the same boat--many of them because of the NVIDIA situation. Realistically, most will not be running on Wayland until a distro makes it the default (like Fedora did with GNOME), which won't happen until there's feature parity with X11. In all likelihood, Wayland is not going to be a practical choice for a great many of our users for years. So it's not like X11-specific code is just totally worthless. That code is what most of our users rely on every day and would like to see improved.

REPOSITORY
  R104 KScreen

REVISION DETAIL
  https://phabricator.kde.org/D12405

To: fvogt, #plasma
Cc: gladhorn, mart, hein, ngraham, graesslin, davidedmundson, plasma-devel, ragreen, Pitel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20180923/fc1df239/attachment.html>