Don't include the spacing after the final letter when measuring bitmap text #1051
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.
As mentioned in #1050,
measure_texterroneously includes the spacing after the final character of a string in it's measurement, for bitmap fonts.This patch fixes it; it probably needs highlighting in the release notes wherever it ends up, in case people (like me!) have dodgy hacks in their code to adjust the returned length.
(tested through to Presto firmware - which was an annoyingly convoluted build, I can tell you - so at least it should be painless to pick up in everything that rolls PicoGraphics in)