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

Scene.onActivate() is called before Scene.onInitialize() #418

Closed
jedeen opened this issue Apr 3, 2015 · 2 comments
Closed

Scene.onActivate() is called before Scene.onInitialize() #418

jedeen opened this issue Apr 3, 2015 · 2 comments
Assignees
@kamranayub
Labels
bug This issue describes undesirable, incorrect, or unexpected behavior good first issue good for people new to open source and Excalibur
Milestone
0.5.0 Release

Comments

@jedeen
Copy link
Member

jedeen commented Apr 3, 2015

This is especially problematic if you have an event listener defined in onActivate() that performs logic on the scene's child actors in onInitialize(). The first time the scene is visited, those actors haven't been instantiated yet.
@kamranayub
Copy link
Member

This is a bug, initialize should be called first, I even say it in the new docs.

@kamranayub kamranayub added the bug This issue describes undesirable, incorrect, or unexpected behavior label Apr 3, 2015
@eonarheim eonarheim modified the milestones: 0.6 Release, 0.5 Release Apr 3, 2015
@eonarheim eonarheim added the good first issue good for people new to open source and Excalibur label Apr 3, 2015
@kamranayub kamranayub self-assigned this Apr 4, 2015
@kamranayub
Copy link
Member

I can tackle this today

@kamranayub kamranayub mentioned this issue Apr 4, 2015
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kamranayub kamranayub

Labels
bug This issue describes undesirable, incorrect, or unexpected behavior good first issue good for people new to open source and Excalibur
Projects
None yet
Milestone
0.5.0 Release
Development

No branches or pull requests
3 participants
@kamranayub @eonarheim @jedeen