Respect BBX offset in glyph parser #1534
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This would close #1521
The commit identified there (39953b7) changed the font parsing to no longer need a left shift, but this meant the offset was no longer used at all.
This introduces a right shift. On the font I was using (https://github.com/MLB-LED-Scoreboard/mlb-led-scoreboard/blob/2bbabaf6c100bd5df197abf76943d08d8c39f3aa/assets/fonts/patched/4x6.bdf) this now re-recreates the exact parse as the older code (except it is now 196 bits wide, rather than 64 bits), and the font characters are now correctly offset.