https://bugs.kde.org/show_bug.cgi?id=482790
--- Comment #14 from Raphael Rosch <kdeb...@insaner.com> --- Well, as luck would have it, I just found this: https://discuss.kde.org/t/per-window-scaling/13620 and running kdiff3 like this: > QT_SCALE_FACTOR=1.5 kdiff3 makes everything huge, but no more artifacts. Scales of "0.5" and "1" do not work (0.5 makes it MUCH worse). Anything from 1.1 and up, all "work". Tried the same with `sqlitebrowser`: > QT_SCALE_FACTOR=1.1 sqlitebrowser And not only does it fix the artifact problem, but also, very interestingly, all the dozens of > QPainter::drawRects: Painter not active > QPainter::setPen: Painter not active messages that used to appear on the console no longer appear at all. The minimum QT_SCALE_FACTOR value to prevent the bug(s) seems to be 1.07 In any case, I have my workaround. Not sure if this means this is now a Qt bug or what, but maybe @cullman can use this information for good. :) More references: https://github.com/qutebrowser/qutebrowser/issues/5211 https://bugs.kde.org/show_bug.cgi?id=390451 (see especially: https://bugs.kde.org/show_bug.cgi?id=390451#c12 ) https://bugreports.qt.io/browse/QTBUG-66036#comment-479182 Given 390451 (and https://bugreports.qt.io/browse/QTBUG-66036#comment-479441 -- which suggests using QRectF instead of QRect to solve the bug mentioned there), can we re-open this? -- You are receiving this mail because: You are watching all bug changes.
