https://bugs.kde.org/show_bug.cgi?id=378523
--- Comment #30 from RJVB <rjvber...@gmail.com> --- I think your guess is as good as mine. There appears to be a consensus among the Qt devs that the style name will continue to work as it does currently, despite some disagreement on the details (like whether the font dialog should always set a style name). Some day there may be API to unset attributes. That's not currently possible, for instance, QFont::setBold(false) will tell the font engine that you want a font that's not bold. That's not necessarily the font you started out with after you called setBold(true). Until that time we'll need some kind(s) of workaround (like the function to recreate a font without stylename I committed to QtCurve) and KDE code should probably aim to avoid using the style name as far as possible. This would have been easier if there were a KFont class... It could be very useful to have a more capable (geeky) font explorer that exposes some more of the information that Qt uses internally, like a font's PANOSE data. I keep reading that style names aren't needed for fonts that can be represented in that system, but AFAIK I have only fonts that are in that category (and wouldn't know how to identify a font that isn't). That makes it hard to test the workarounds and to figure out if code can determine reliably when a style name can NOT be avoided. -- You are receiving this mail because: You are watching all bug changes.
