Add convenience methods for determining if collisions are starting or stopping #529
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.
Objective
It can be tricky to match and handle all of an entity's collision states in a single event loop. I routinely find myself writing code like this:
Solution
Add
Contacts::collision_started
andContacts::collision_stopped
to more conveniently check these conditions.Changelog
Added
Contacts::collision_started
andContacts::collision_stopped
for more conveniently checking if a collision just started or stopped.