Thanks for the additional background info.
As you suggested, I’ve raised a bug around this particular capability “Request for a use-native-DPI setting” in which I’ve tried to outline the use-cases where such a setting might be important. I wasn’t sure exactly where it belonged, I raised it against kwin. Others may wish to add their own perspectives to the bug.
This option is really missed by me. Please, bring it back in Plasma 6. You can call me dumb or idiot, but only this option works for me. Adjusting the scale in the display settings doesn’t solve the situation. Everything becomes blurry. I hope the geniuses behind this project humbly pay attention to this request. Force Font DPI is very necessary. It doesn’t harm anyone and it’s another feature for the user.
Sorry for the late reply. I’ve been pretty busy the last couple of weeks. If you are still interested, I will gladly explain why I don’t want everything scaled on a global level.
The first and most simple reason is, that the size of most things is just fine. I don’t need everything to be bigger, because most things are just fine the way they are and I don’t have the need to fix something that is not broken.
The second Reason would be, that if I do scale everything globally, I would need to set it to 150% to get the document size match it’s physical paper version. So, my whole UI just gets insanely huge, which is just absolutely unnecessary and annoying.
What I don’t understand is, why you are writing about the dpi feature as it was some kind of wonky workaround constantly breaking things. I used it for years and it always worked fine. It just did what it said it would do – nothing more, nothing less. It was the only tool I needed to achieve what I think is a reasonable thing to want. I don’t had to tweak or tinker anything. I just used this feature as I think you initially intended it to be used.
I do see, that you probably have to deal with people, who don’t know what they are doing regularly. They click, tune and tweak everything they get their cursor on and ignore every warning you put in their way. This way they either find their workaround to something you would rather be notified about, so you can fix it, or it causes problems and breaks things, which they then come to you with. I can only imagine how tiresome and exhausting this must be. I do understand if you want to limit the ways people are able to sabotage themselves and the potential growth of the whole project. I just don’t feel great about this resulting in decreased usability
for people who used things as they were intended to be used.
Never the less, KDE Applications and the Plasma Desktop have become really awesome in general. I always liked and appreciated them very much and they constantly get better. The everything-work-properly-out-of-the-box-thing came a long way since I remember starting to use KDE. You all did a really great job here. Thanks for the effort and your willingness to discuss these matters with us.
A quick note for anyone reading this thread and wanting a workaround:
I’ve updated the bug-report/feature-request to include what is probably the most straight forward workaround to get the physical and desktop DPI into agreement, basically:
echo 'export QT_USE_PHYSICAL_DPI=1' >> /home/testuser/.config/plasma-workspace/env/hidpi.sh
(Perhaps this might eventually be set from a small GUI script. One that creates the setting and does a kwin-replace. Worst case it could require a re-login to bring it into effect.)
Thanks for explaining the use case, that’s really helpful.
@ngraham just to be sure I understand: the file ~/.config/kcmfonts is not taken into consideration in Wayland session, is it?
I mean, if I set it to
[General]
forceFontDPI=120
this will be considered only in X11, not in Wayland, right?