Frustum Visual ABI compatibility changes #1102
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.
🎉 New feature
Summary
Implement ABI compatibility changes for the Frustum Visual feature (#1095) so that it can be backported to gz-rendering9. The approach is similar to #845 which uses the
SceneExt
class for creating the visual frustum to prevent overriding virtual functions (which breaks ABI). The official functions for creatingFrustumVisual
classes are commented out (instead of being removed) to keep the diff withmain
minimal.I also added a unit test for the FrustumVisual class.
Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining
Signed-off-by
messages.