Eliminate race condition to improve coordinate accuracy and reliability. #18
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.
Was experiencing occasional touch coordinate errors, particularly when rapidly pressing the touchscreen. The existing code measured the x and y coordinates then would check to see if the z (pressed) value exceeded the touch threshold value. In some cases, the x and/or y coordinate value would reflect a measurement made before or while the screen was being pressed, resulting in a significant coordinate offset error even when averaged.
The modification changes the logic; the x and y values are not measured until after the z value exceeds the threshold, assuring coordinate accuracy and stability.
Tests without the changes experienced approximately 2 errors per 50 presses. The error rate dropped to 0 with the updated code. Tests were performed using CircuitPython 7.0.0 on a PyPortal Titano using DisplayIO Buttons and VectorIO objects.