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 is a set of random collection stuff I stumbled across while chasing something completely unrelated. Taken in no particular order:
CAM_FEEDBACK_PIN
, (reboots are always required to detect shifts if it involved the edge feedback pin).feedback_pin_timer
and does it before the timer is installed. This is run at 1 kHz, so it's worth keeping this reasonably short, and with the reboot required if you shift pins under some circumstances I didn't feel that this was a large behavior shift._camera_triggered
to false on boot.I believe this fixes the double feedback event when taking the first photo.AP_Camera::check_trigger_pin(void)
toAP_Camera::check_feedback_pin(void)
to better reflect what it's trying to do. (This is still a very confusing section of code, this is just where I drew the line for limiting refactoring).I need to test this (probably tomorrow) before we look at merging, but I'm most hopeful about 3, as the double feedback event is really frustrating.