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

2.1: Fixes two problems with Area2D and remove_child() #7934

Merged
merged 1 commit into from
Mar 4, 2017

Conversation

pwnSquirrel
Copy link
Contributor

  • When one of two or more overlapping Area2Ds is removed with remove_child(), it doesn't try to report to the other one anymore
  • When overlappinng Area2Ds are removed woth remove_child(), _enter_tree and _exit_tree signals are now properly disconnected upon removal

Should fix #7919 and #7507. Part of this PR is like #7508, but this one is for the 2.1 branch.

- When one of two or more overlapping Area2Ds is removed with remove_child(), it doesn't try to report to the
other one anymore
- When overlappinng Area2Ds are removed woth remove_child(), _enter_tree and _exit_tree signals are now
properly disconnected upon removal
@akien-mga akien-mga added this to the 2.1 milestone Mar 4, 2017
@akien-mga akien-mga merged commit c58c490 into godotengine:2.1 Mar 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants