Repository navigation
Test: Let the remembered TextFieldState render test take up to four frames - #88
Merged
Merged
Conversation
…extFieldState On develop the single render after the write drew identical pixels (0 differ) although the state held the new text; the field's text-change handling plausibly lags one frame. The assertion is unchanged, so a write that never reaches the draw still fails.
This was referenced Oct 3, 2026
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
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.
Closes #87
Test robustness only: after the Python write the test now renders up to 4 frames and stops at the first that differs; the assertion (>10 pixels differ) is unchanged, so a write that never reaches the draw still fails. Rerun on develop: compose 115/0, 'ink 15678 -> 15678 px, 930 pixels differ after 1 frame(s)'.