Handle humans spamming shutter or focus buttons. #64
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
The latency for BLE comms can easily exceed any human click speed. If this happens, we lose button events. Handle this by forcing an M5.Update() immediately after sending a command to the camera. Whilst here: - change the loop semantic (coz I can) - handle the shutter control back button without conditional compilation - let the M5Unified library work out if the buttons actually exist
gkoh
deleted the
63-quickly-pressing-buttons-in-shooting-mode-causes-functions-to-get-stuck-on
branch
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.
The latency for BLE comms can easily exceed any human click speed. If this happens, we lose button events.
Handle this by forcing an M5.Update() immediately after sending a command to the camera.
Whilst here: