Adding frame.keep() API #1015
Merged
Adding frame.keep() API #1015
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
(cherry picked from commit 4c06c54f1cdb26dd8ad06c1fc165a06f79c1f5b2) # Conflicts: # src/archive.cpp # src/archive.h # wrappers/python/python.cpp
|
Do you have to call ~frame() to deallocate memory after popping from say, a queue? |
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.
Following-up on #1000 (Saving frames for future processing) and related
This PR introduces
keepmethod onrs2::frameobject (available to C, C++, python and .NET right now) that communicates the intent to hold-on to that frame for longer processing.