Created attachment 140520 [details] Screen recording SUMMARY I have set the overall scaling via the Display and Monitor KCM to 200%, this changes the "force dpi" setting in the fonts KCM automatically. Highlighting the changes of the KCM in respect to their default state does not show that this setting has been altered. (Please see the screen recording.) Clicking on "reset to defaults", however will disable "force dpi". Changing it now back to the value suggested by the "Display and Monitor" KCM results in: 1) An inline message, suggesting to better apply the configuration automatically via the Display and Monitor KCM. (Fair!) 2) The "force dpi" checkbox NOW becomes orange, highlighting it was changed. I find this situation rather tricky: Resetting KCM A, which was automatically adjusted by another KCM B, which is however left untouched by this reset, is not optimal. It'd be better a) to indicate, that this setting was adjusted by another setting and not by the user themself b) to ask to keep the settings, which were altered by other KCMs or to reset both to keep an consistent state. In both cases of b) it should be explained which settings are interrelated. SYSTEM Operating System: openSUSE Tumbleweed 20210730 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.4-1-default (64-bit) Graphics Platform: X11
Probably we should not highlight the DPI setting as having changed from its default setting at all; technically what has happened is the value of its default setting itself has changed when you set the scale factor.
(In reply to Nate Graham from comment #1) > technically what has happened is the value of its > default setting itself has changed when you set the scale factor. Quiet right, but now you unfortunately have changed the title of this issue. It thought more of it as a meta-bug for cases like these.
If it affects other KCMs too, we would need separate bug reports for them. Meta bug reports are never actionable. :) See https://community.kde.org/Get_Involved/Issue_Reporting#One_issue_per_Bugzilla_ticket
(In reply to Nate Graham from comment #3) > If it affects other KCMs too, we would need separate bug reports for them. > Meta bug reports are never actionable. :) I know that multiple issues per thread are not very efficient. Of course I can open bugs for each component and then discuss in all of them the very same matter: What do to do in this situation, what is the common goal for all these reports. Anyway, I don't mind really, let's stick here to the font KCM for now and get back to topic. ;)