Debug screen support #101
Merged
Debug screen support #101
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
|
I should have also noted that I abstracted the code to get the version number into a function as it's now used in more than one place, efficiency yay! |
chrisys
approved these changes
Jul 22, 2023
|
Tested on my Zero 2 W, all seems fine as you'd expect! Looks great - thanks for another great contribution 👍 |
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.
Fixes #100
Adds a debug screen either replace the splash screen or the train departure info (permanent mode).
Setting
debugtoTruereplaces the main screen permanently.Setting
debugto an integer (except1, because1 == True) will replace the NRE attribution screen with the debug info fordebugseconds. (This option hides the clock as it is a static display withtime.sleep())I've tested it on a 3B with no detrimental effects but not got my Pi Zero boxed up into a display to real-world test it yet, although I don't anticipate any performance issues.
I've also added what I believe to be the correct code to render this on both screens but again I haven't got my testing ready for that just yet!