D9070: KDE platform plugin: don't force default stylename on user-specified fonts

[René J.V. Bertin]

rjvbb added a comment.


  It depends a little bit what kind of call you make. But yes, certain "conflicting" attributes can no longer be set. A particular example reported by many is setting bold. If you do `setStyleName("Regular")` on a Qfont, `setBold(true)` will no longer have the intended effect, or possibly not the same effect (apparently you can also end up with an emboldened version of the font, rather than with the actual bold version).
  
  Have you ever worked with professional typesetting, drawing of page-layout applications like InDesign or Illustrator? There you don't set a font to bold, you select another typeface from among the ones you have installed. This is of course how fonts are designed and implemented but most of expect that "old-fashioned inconvenience" to be hidden. IOW, flip a font to bold by hitting Ctrl-B and you get "Foo Bold" rather than "Foo Regular-or-Whatever-you-had turned into something looking bold". Calling `setStyleName()` brings back a bit of that old-fashioned "pedantic" nature.

REPOSITORY
  R135 Integration for Qt applications in Plasma

REVISION DETAIL
  https://phabricator.kde.org/D9070

To: rjvbb
Cc: fvogt, plasma-devel, ZrenBot, progwolff, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20171130/0b930384/attachment.html>