[Screenshot Generator] Add explicit Toast duration
, additional code comments
#613
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.
Description
Light refactor of
RemoveSDCardToastManagerThread
to give the screenshot generator more explicit control over that Toast.Screenshot generator now sets
RemoveSDCardToastManagerThread.duration=0
to guarantee that the "infinite" Toast would never block during the screenshot generation. It was succeeding (not blocking) before becauseMicroSD.is_inserted
checksSettings.HOSTNAME == Settings.SEEDSIGNER_OS
, but this took too much digging to understand that Toast's behavior in the screenshot generator.How the Toast screenshots are rendered at all is quite confusing so additional step-by-step explanatory comments were added.
This pull request is categorized as a:
Checklist
pytest
and made sure all unit tests pass before sumbitting the PRIf you modified or added functionality/workflow, did you add new unit tests?
I have tested this PR on the following platforms/os: