Visual cloning: check for null children and recursively delete cloned visuals if failure occurs #434
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.
Signed-off-by: Ashton Larkin ashton@openrobotics.org
🦟 Bug fix
Summary
Follow-up to #397
If cloning a visual fails, we should destroy the top-level cloned visual recursively in order to ensure that all cloned child visuals are also destroyed. I also added a check to make sure that the child visual to clone isn't
nullptr
.Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge