Repository navigation
LCD subpixel AA
#8747
Replies: 2 comments 1 reply
|
Update: @mikael2 has since opened two draft PRs that implement this design:
So instead of starting my own implementation, I would rather help get these in. I can test them on Linux at 1x and 2x with the shadcn-egui gallery, which shows a lot of small UI text. @emilk: is an opt-in path like this something you would merge, in principle? If yes, a hint on the open question in #8752 (whether every font-texture mesh goes through the new pipeline) would help unblock it. |
0 replies
|
Just my 5c but pretty much everyone is phasing out subpixel AA because of high DPI screens? E.g. all the new WinUI stuff that Microsoft makes isn't using it anymore. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
@emilk @valadaptive — a question before starting to code.
On 1x displays, egui text looks noticeably softer than browser text next to it. The browser uses LCD subpixel AA, egui uses grayscale (Inter 14 px at 1x, enlarged 3x; Chrome 155 on Linux left, egui 0.34 right):
Now that text runs on Skrifa + vello_cpu (#7694) and glyphs live in a separate
GlyphAtlas(#8501), would an opt-in path fit egui? It would rasterize glyphs with RGB coverage, blend them per channel with dual-source blending in egui-wgpu, and take the subpixel order (RGB/BGR/none) fromTextOptions. Grayscale would stay the default and the fallback.If yes, I would be willing to work on it.
All reactions