Stop mixing single and double tap detection. #17
Merged
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.
I haven't updated the guide that goes with this yet but will after the pull is accepted. We won't release it until the CPX library is forwards compatible.
The examples related to tap detection were tested on a CircuitPlayground Express.
This changes the API to have single boolean
tapped
property(formerly read_click).
This change aligns the behavior with the expectation that a tap
thats part of a double tap does not register as a single tap. It
will now only detect single or double taps as set by
set_tap
.Names with click were renamed to tap so they align with what is
actually happening rather than the data sheet names. A comment in
the code points this out.
The tap example now also deduplicates taps because tap detection
holds the status for a while.