It turns out there were some inconsistencies, so hopefully I can make an improvement here regardless. The second link was interesting and had me looking all over the codebase for places where we mess with the font hinting settings. The link seems to suggest that if we were having an issue where DirectWrite was unable to display the font correctly, we should be getting some sort of 'halo' effect because of how the colors bits are swapped around? But, regardless, DirectWrite is something I need to look into because Qt6 now relies heavily (entirely?) on that for rendering on Windows. So, I'm not 100% sure if the top one is relevant or not. In 3.3, this has broken completely and the UI look just wrong irrespective of font and antialiasing option, as shown in the screenshots above. In 3.2, it was possible to work around this by setting "Segoe UI" and "Consolas" as the application and view font name respectively, plus setting the antialiasing to Subpixel. Repeat 1, then set font> "Font Antialiasing Style" to any desired option.Set font.app > "Application font name" to "Segoe UI".Go to Settings, type font in the search bar.Please provide all steps required to reproduce the behavior: having blurry widgets even with the default Inter typeface. While I could work around it in that version (see below), 3.3 has broken it completely. The font antialiasing has been failing for me since at least 3.2. Binary Ninja Version: Personal (Build ID e34a955e).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |