https://bugs.kde.org/show_bug.cgi?id=450378
David Edmundson <k...@davidedmundson.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INTENTIONAL CC| |k...@davidedmundson.co.uk Status|REPORTED |RESOLVED --- Comment #4 from David Edmundson <k...@davidedmundson.co.uk> --- >Perhaps it's easier to first implement it on X11. Definitely not, we have no input redirection and all clients are aware of the geometry of other windows; if this doesn't match cleints everything explodes. > Wayland Whilst technically possible, it means a different co-ordinate system between compositor and clients. We did put some infrastructure for xwayland in the upcoming release so xwayland as a whole to have a different scale. (exposed differently to shift+drag). I only covered the protocols used by xwayland which is considerably smaller than all the wayland protocols but I have an idea of how much work is involved! Not impossible, not trivial. >E.g. if you have a 4k display with 1.25 scaling, the current scaling method on >Wayland would give a 6144x3456 (4k / 1.25 * 2) buffer to a fullscreen >application such as the always-present desktop background. That's changing. It's going to give you the same sized buffer starting soon. Lets revisit after this and the xwayland change and the fractional scaling branches have landed and see how much of a use-case remains. -- You are receiving this mail because: You are watching all bug changes.