This repository has been archived by the owner on Apr 1, 2020. It is now read-only.
[WIP] Fix #541 - Font rendering improvements #753
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This also fixes #541 |
bryphe
changed the title
… resize, or the delta tracking of cells
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are still cases where the text is blurry during rendering, due to subpixel anti-aliasing. Setting the
{alpha: false}flag helps in this case, but has the downside that we can no longer have a transparent background.This is some experimentation around rendering improvements, if we deprecate the background.
This also opens up the ability to cache words / letters as images, and use
context.drawImageas opposed todrawTextfor frequently used tokens, which could potentially speed up rendering later. That strategy isn't feasible currently, because the text is blurry.