Remove ownership of I2C and pass as argument to functions instead. #21
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
If an instance of HT16K33 owns the I2C instance, then it's not possible to control multiple HT16K33 instances over the same I2C line. This is true when communicating with multiple devices even if they're not HT16K33 objects. This change allows multiple devices to be communicating over the same I2C line.
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.
If an instance of HT16K33 owns the I2C instance, then it's not possible to control multiple HT16K33 instances over the same I2C line. This is true when communicating with multiple devices even if they're not HT16K33 objects.
This change allows multiple devices to be communicating over the same I2C line.
You can see usages of this in https://github.com/Nashenas88/sparkfun-alphanum4