Snap to tick with detections #596
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.

Summary
In this PR we suggest a solution to #585 with a new new view setting "Snap to tick with detections". When checked, we will snap to the next tick with detections when using one of the three ways to navigate images:
Comments and limitations
At the moment, the timeline response from backend does not include processing status for images. From a frontend perspective, we only know if a timeline tick has detections or not. In practice a processed image might not include any detections, this is why I named the view setting this way, without mentioning processing status.
Another detail to mention is that a timeline tick might include multiple images with detections. At the moment, backend only returns the id for the "top image" in the interval. This is why we call the view setting "snap to tick" instead of "snap to image". If the timeline endpoint could provide some more info about images in an interval, we could update this. We have discussed one tick/image before @mihow . If not to much data do handle at once, I think this could reduce some limitations...?
Regarding the first capture that will be visible, currently this ID is specified by the backend session response. Do you think we should change this, to return ID for the first capture with some detections?
Screenshot