Fix SPI_Buttons constructor procedure#164
Merged
Ultrawipf merged 4 commits intoUltrawipf:developmentfrom Jan 16, 2026
Merged
Conversation
Ultrawipf
force-pushed
the
development
branch
from
dd3010c to
cbd64db
Compare
Owner
|
Sorry for the delay, i have to check if it will properly discard the changes from already applied commits |
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
2 participants
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.
Currently the SPI_Buttons constructor overwrites whatever happens in
setConfig()(as called fromrestoreFlash()) with hardcoded values which, from the looks of it, should break the PISOSR compatibility.