Added working examples using GPIOZero with Tkinter and Pygame #56
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
|
Looks bad actually |
|
@Parth099 elaborate |
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.
For issue BP-131, I was tasked with solving an incompatibility between GPIOZero and Pygame Zero.
After conducting some tests, I determined that it would be easiest to eliminate our Pygame Zero dependency and build out our own Pygame helper methods alongside GPIOZero.
In this branch, I included two new directories
Where I include working examples of GPIOZero interfacing with the Pygame and Tkinter libraries.
These examples assume access to 4 switches on GPIO pins 5, 6, 13, and 19 on the Raspberry Pi.