Only set bounds when annotation is visible. #14
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 set bounds function is actually kinda cpu intensive. I noticed that
when there are thousands of bounding boxes in your video sequence, it can add
seconds to moving bounding boxes, creating bounding boxes, and switching to
another image frame. reduces the ammount of times set bounds is called
by only calling the function when annotations are set to appear
visibile.
This is the time it used to take to draw annotations for a video with a few hundred bounding boxes
this is the time it takes to draw annotations after.