Repository navigation
Conversation
The three byte-mode renderers repeated the encode and its wipe, and two repeated the module loop. The 5000-script replay and the render tests draw the same frames.
This file contains hidden or 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
1 participant
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.
The three byte-mode QR renderers each repeated the encode and its wipe, and two repeated the module-drawing loop. Now there is one
encode_bytesand onedraw_modules. The public API is unchanged.Verified with: the 5000-script replay (0 runs differ),
ctestplain and under ASan/UBSan, Python tests, firmware built twice inespressif/idf:v5.5.4with audit andcmp.