Sprite vs Tilemap can now check for overlap, without trying to separate #1810
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
|
Anything else I can do to get this merged? It would help greatly with some current issues I am facing. |
photonstorm
added a commit
that referenced
this pull request
Jun 17, 2015
Sprite vs Tilemap can now check for overlap, without trying to separate
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.
Currently, the ability to check for an overlap between a Sprite and Tilemap does not exist. This is because the overlapOnly property from collideHandler stops getting passed down the chain (or is passed, and ignored). This update brings the overlapOnly property down to the "separateTile" function. Within that function, an intersection between the Sprite and Tilemap will return true and not proceed with the separation.