Added function to retrieve ShapeFrames from CollisionGroups #711
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
|
Reviewed 3 of 3 files at r1. Comments from Reviewable |
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.
I wanted to be able to make deep clones of
CollisionGroups, so I've added the ability to access the ShapeFrames of aCollisionGroup. The deep clone will still need to be done manually by the user for the time being for a variety of reasons, such as:ShapeFrameownership is still a complex issue without a decisive solution.CollisionGroupwill probably need to belong to a differentCollisionDetector, since the motive for deep cloning is usually multi-threading, and I can't think of an obvious API for automating this right now.This change is