Fix Debounce example to work as described #1192
Merged
Conversation
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
This alters the debounce example code to toggle the LED rather than just use the button state to set the LED state. Fixes #293
ghost
assigned
Fede85
added a commit
that referenced
this pull request
Apr 16, 2013
Fix Debounce example to work as described
|
Thanks. |
oriregev
pushed a commit
to oriregev/Arduino
that referenced
this pull request
Dec 20, 2013
Fix Debounce example to work as described
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.
This alters the debounce example code to toggle the LED rather than just use
the button state to set the LED state. The comments and description seem to imply that this is the intended behaviour.
This came up on reddit today: http://www.reddit.com/r/arduino/comments/15ko75/arduino_tutorial_2_digital_debounce_problem and I also noticed a previous bug referencing the same issue (#293).