add onImageSnapped, onSequenceAcquisitionStarted, onSequenceAcquisitionStopped events #538
+40
−0
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.
These events would make it easier for the application side to "know" that a new image buffer is available to display.
As with most callbacks here, I'm aware that this implementation is slightly leaky (in that some devices may snap/start/stop without these events being emitted). That's certainly less than ideal, but it's still better than not knowing at all, and covers cases where the core API itself is used to snap/start/stop