Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make collision handling more robust #10

Open
ndarilek opened this issue Nov 18, 2013 · 3 comments
Open

Make collision handling more robust #10

ndarilek opened this issue Nov 18, 2013 · 3 comments

Comments

@ndarilek
Copy link

I find myself missing Begin/EndContact methods. The current framework is good enough to detect when a collision is happening, but not when it begins or ends.

I'm not sure what the best way to handle this is. Maybe onContactBegin/onContactEnd functions similar to onContact?

Failing that, how would one easily detect that a collision began to play an appropriate sound?

Thanks.

@shogoki-vnz
Copy link
Owner

I will try to look a it this weekend

@ndarilek
Copy link
Author

Excellent. At the moment I have a very hacky check in my EnterFrame to detect new collisions, but it'd be good to refactor to onContactBegin/End or something similar.

@ndarilek
Copy link
Author

ndarilek commented Feb 1, 2014

Cool, any updates? I keep finding places that'd benefit from knowing when a collision begins or ends. Would a PR providing this functionality be accepted?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants