Bug fix: A changed object might not affect object on same layer #102
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.
This is a bug fix
(See unit test)
If Partial Resolving (using cache) is enabled:
On Layer
L0
, we have objectA
andB
.If object
A
has changed between resolves, this should affectB
, since they are on the same layer and collide with eachother.Currently, this is not taken into account during a resolve.
If Partial Resolving (using cache) is enabled:
If an object is changed between resolves, any object on the same layer (ie can be affected by the change) will be re-resolved.