https://bugs.kde.org/show_bug.cgi?id=336089
--- Comment #38 from Thomas Lübking <thomas.luebk...@gmail.com> --- (In reply to Martin Klapetek from comment #33) > But I'm thinking we could just add brand new font rendering > widget to the kcm that replaces the old one and leave everything > else in place (including the bitrotted code). Hummm... that kicked something in my brains. The view isn't only required for the kcm, but also for kfontview. In addition it must be able to handle *specific* fonts from files, which are not (yet) installed in the system - so I guess the cause for the custom code was either the absence of QFontDataBase before Qt 4.2 or it's dependency on fontconfig? @Thomas S.: you'll have to make use of the class when/if porting the view. Reg. the multiselection: the view replaces the preview by a list of the selected font names in a QLabel here then (what oc. works like any regular font rendering), but the broken rendering does look like an issue with the color/alpha channels - what you indicate the "wrong" visual id or picture format is selected (yet even if, the code is too complex if the task can be done by QFontDatabase + QPainter) -- You are receiving this mail because: You are watching all bug changes.
