Bug 402381 - "exclude range from anti-aliasing" option does not trigger option change (apply button is disabled after change)
Summary: "exclude range from anti-aliasing" option does not trigger option change (app...
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_fonts (other bugs)
Version First Reported In: 5.14.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-20 14:27 UTC by Till Schäfer
Modified: 2019-06-07 11:03 UTC (History)
3 users (show)

See Also:
Latest Commit: https://commits.kde.org/plasma-desktop/df81b30e11a69d4d35355d7e8b5a62347737ad4d
Version Fixed In: 5.16.1
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Till Schäfer 2018-12-20 14:27:33 UTC 
SUMMARY
When the checkbox "exclude range from anti-aliasing" is toggled, it is not recognized as change by the fonts kcm. This is observable by the following two indicators: 
- The apply button does not get enabled. 
- quitting the font kcm does not raise apply/discard/abort dialog


SOFTWARE/OS VERSION:
Linux: Gentoo Linux
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.53.0
Qt Version: 5.11.3
Comment 1 Till Schäfer 2018-12-20 14:37:53 UTC 
there are more oddities, when clicking the button defaults in the fonts kvm, change to another kcm and discard the changes, and then switching back to the fonts kcm, the option "exclude range from anti-aliasing" is always enabled with 0 to 0 exclude range.
Comment 2 Patrick Silva 2019-02-23 20:07:27 UTC 
I can confirm the problem described in comment 0.

Operating System: Arch Linux 
KDE Plasma Version: 5.15.1
KDE Frameworks Version: 5.55.0
Qt Version: 5.12.1
Comment 3 Fabian Vogt 2019-06-07 11:03:33 UTC 
https://phabricator.kde.org/D21640 fixes the exclude button tracking and some other oddities. Will be part of 5.16.0 or 5.16.1.