Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

slint font rendering is very poor, how to solve it #6365

Open
xiacc-cn opened this issue Sep 28, 2024 · 2 comments
Open

slint font rendering is very poor, how to solve it #6365

xiacc-cn opened this issue Sep 28, 2024 · 2 comments
Labels
a:text Text rendering, fonts, Text input (mS,bF) need triaging Issue that the owner of the area still need to triage

Comments

@xiacc-cn
Copy link

See the picture below
image

@ogoffart ogoffart added need triaging Issue that the owner of the area still need to triage a:text Text rendering, fonts, Text input (mS,bF) labels Sep 30, 2024
@ogoffart
Copy link
Member

ogoffart commented Oct 1, 2024

Do you know what renderer/backend you are using? There are some differences between skia and femtovg.
I think skia is used in the live preview, while femtovg is the default in a rust application unless you enable skia with a feature flag.

@nproux
Copy link

nproux commented Oct 2, 2024

Not OP, but I ran into the same issue and changing to the skia renderer seems to resolve it for me. The font rasterization in the default renderer and default text family (for Windows 11 environment at least) seems to be impressively bad right now. For reproduction I was using English characters at font sizes 20px and 24px, both bold and regular, with a Rust backend. Build and run in release mode and you should notice it right away.

It might be a bug in the renderer rather than Slint itself, but I suggest that what Slint picks as the default renderer should probably be biased towards something that visually looks decent. New users aren't likely to dig into details of how to make things better if their initial testing has pretty poor results. That said your team might have other concerns I'm not aware of that make the current default choice the better tradeoff, so feel free to ignore me on that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:text Text rendering, fonts, Text input (mS,bF) need triaging Issue that the owner of the area still need to triage
Projects
None yet
Development

No branches or pull requests

3 participants