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.

Sign up for GitHub

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

Jump to bottom

NotificationNode is not entered and exited. #13477

Closed
pandamicro opened this issue Aug 20, 2015 · 1 comment
Closed

NotificationNode is not entered and exited. #13477

pandamicro opened this issue Aug 20, 2015 · 1 comment
Assignees
@ZhangMenghe
Milestone
3.9

Comments

@pandamicro
Copy link
Contributor

When setting notification node using Director::setNotificationNode, the target node's onEnter haven't been called. When old notification node replaced by new one, it's onExit haven't been called neither.

The consequence is that the notification node can't be scheduled. And action won't take effect neither
@pandamicro pandamicro added this to the v3.9 milestone Aug 20, 2015
@pandamicro
Copy link
Contributor Author

@ZhangMenghe , web engine need this modification too

This was referenced Aug 21, 2015
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ZhangMenghe ZhangMenghe

Labels
None yet
Projects
None yet
Milestone
3.9
Development

No branches or pull requests
2 participants
@pandamicro @ZhangMenghe