https://bugs.kde.org/show_bug.cgi?id=389329
David Edmundson <k...@davidedmundson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |k...@davidedmundson.co.uk
--- Comment #1 from David Edmundson <k...@davidedmundson.co.uk> ---
1) Those apps are probably running in X. There are very few apps that fall into
the valley of having both have high DPI support and aren't being ported to
wayland. It's an issue that will solve itself by the time wayland is
mainstream.
2) There's another bug report for that somewhere
3) I don't understand, can you include a screenshot. Ideally as a new report.
4) What do you mean by tiling? Can you include a screenshot
5) As in you can only see the top left quarter when fullscreen?
If so will be fixed soon with the new xdg-output and new xwayland.
If you mean something else, please include a screenshot.
As for the rest, duly noted. I'm happy to fix any bugs, but I'm not going to
revert any defaults.
Your ideas miss some key aspects of how things work, and why they can't be done
the way you suggest.
You can follow more on the threads of the wayland mailing list.
>So instead using a 2x scale, we need a 0.5x scale for peasant displays
If the app is scaling at 2x, and on a 1x screen, that's *exactly* what happens.
If the app can't scale to 2x then you're not in a position to halfscale it.
You can't just assume bodge "scaling" with font DPI, because an app has no way
to report whether it's following that or not.. and we can't add a protcol for
that into existing applications.
>I think things like QT_SCALE_FACTOR should be only used for mitigation of
legacy applications.
That would mean kwrite would be tiny?
--
You are receiving this mail because:
You are watching all bug changes.
