https://bugs.kde.org/show_bug.cgi?id=378523
--- Comment #79 from Ahmad Samir <a.samir...@gmail.com> --- I didn't go for dropping that property unconditionally, because I took the path of least destruction, doing the minimum amount of removal to get setBold(true) to work properly. IIUC, the styleName property is still useful in some cases https://invent.kde.org/frameworks/kwidgetsaddons/-/commit/b52622993b45a61c4060d19517a5c3b833b3b854 (the Noto font family is one widely-used example of a family with many styles). And there could be other cases (that I am not aware of) where the styleName property is actually useful Also the fonts KCM has switched to using KFontChooserDialog (instead of QFontDialog), the former doesn't return fonts with the styleName set for regular-like font styles. > On a related note: wouldn't it be possible to obtain a QFont that has never > had the styleName property set internally, and then add it, rather than > depend on being able to strip it? That's what the commit from comment#77 is trying to do; if the styleName is never added to the config file when saving the settings, then when loading those settings, the resulting QFont won't have the styleName property set. -- You are receiving this mail because: You are watching all bug changes.
