SUMMARY If the "Anti-Aliasing" option is unchecked, only "Window Title" correctly renders as aliased. All other elements on the panel continue rendering as anti-aliased. STEPS TO REPRODUCE 1. Uncheck "Anti-Aliasing" 2. Open an app like Dolphin OBSERVED RESULT Using Dolphin as an example, the window titlebar will be correctly aliased, but everything else in the window will be anti-aliased. EXPECTED RESULT For everything to be completely aliased, however if there has to be a bug, it should be a consistent bug.. the window title should also be anti-aliased in that situation. SOFTWARE/OS VERSIONS Operating System: SteamOS 3.4.6 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.13.0-valve36-1-neptune (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION I actually often do use truetype fonts that have been hinted to work properly aliased. I feel the need to make this comment because I've seen a number of comments in bug reports saying "why would you want ugly fonts?". My response to that is, if you use a properly hinted font designed for 1-bit, it'll be crisp and clear just like bitmapped fonts in the console. It is correct that if the font is not hinted and AA is turned off, it will look bad on a lower resolution display. Also, the higher resolution a display is, the less and less you need anti-aliasing, in other words, if you're on 4K, 5K, 6K, 8K, etc. resolution displays, you will actually WANT to have anti-aliasing (and hinting) turned off. In any case, the bug should demonstrate a consistent behaviour with the rest of the screen elements.
Incidentally, there may be some interplay with QT here for apps like System Settings, Dolphin, etc. who do not respect the settings. In Windows, I stopped updating qBittorrent past a certain version because an update to QT caused the app to enforce anti-aliasing when previously it respected the OS setting to have it disabled. Should this bug be properly filed against QT? It is a regression, since it was working correctly before a certain version number.
Yeah, it sounds like this is a Qt bug. If you could submit it there and drop a link to it here, that would be nice!
(In reply to Nate Graham from comment #2) > Yeah, it sounds like this is a Qt bug. If you could submit it there and drop > a link to it here, that would be nice! Hi, I have done so now . A surprising amount of different AA-related bugs on their tracker. https://bugreports.qt.io/browse/QTBUG-114405