https://bugs.kde.org/show_bug.cgi?id=391691
David Edmundson changed:
What|Removed |Added
CC||linuxhi...@gmail.com
--- Comment #8 from Davi
https://bugs.kde.org/show_bug.cgi?id=391691
Nate Graham changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=391691
Nate Graham changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=391691
--- Comment #5 from Nate Graham ---
I'm a person who's uptight about fonts, but I'm also realistic: fonts without
sub-pixel anti-aliasing are vastly better than fonts that are blurry and
pixellated! I often use a non-integer scale factor (1.1x) and font
https://bugs.kde.org/show_bug.cgi?id=391691
--- Comment #4 from David Edmundson ---
Other way round.
Disabling native rendering "fixes" it.
Downside is you don't get native rendering. (with correct subpixel hinting and
whatever other native things you might have)
To me it looks the same, but s
https://bugs.kde.org/show_bug.cgi?id=391691
Dr. Chapatin changed:
What|Removed |Added
CC||bugsefor...@gmx.com
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=391691
--- Comment #3 from Nate Graham ---
Thanks David. So forcing the use of Text.NativeRendering at non-integer scale
factors will resolve it? What's the downside to this?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=391691
--- Comment #2 from David Edmundson ---
> there's only one
There are many. Follow the components import.
>and that porting it to QQC2 will resolve the issue?
It will make no difference.
Only relevant thing is Text render type. Text isn't part of QQC
https://bugs.kde.org/show_bug.cgi?id=391691
Nate Graham changed:
What|Removed |Added
Summary|Logout overlay has blurry |Logout overlay has blurry
|pixe
