SceneManager additions

ndoss

We've made the following additions to our version of scene manager:

1. Added option to SceneManager:changeScene to filter out a list of events during screen transitions
2. Added option to SceneManager:changeScene to pass user data to scene constructors
3. Moved delta addition to end of onEnterFrame so that time goes from 0 to 1 instead of (0+detlaTime) to 1
4. Added additional "real time" argument when dispatching transition events. Along with change #3, a user can now look at the additional argument to determine when a transition begins (true time=0) and when it ends (true time=1). We're using this to be able to do things like adding (removing) sprites when the transition begins (ends).

@atilim: I forked the Gideros scene manager github project (https://github.com/ndoss/Scene-Manager), made these changes, and sent you a pull request in case you want to pull them into the official scene manager.

--ND

Although it's not very interesting, here's an example of changes 1, 3, & 4:

Zoyt

Like it! Helpful!

avo

I really like the option of passing a variable to a new scene.

I also just spent half an hour figuring out why you would want to pass the 0,1 or percent complete to the actual transition function. Then I realized it was so you can add effects during the transition. Then I realized that's exactly what the video you posted showed and I made this face #-o for not realizing it sooner than that.

Thanks @ndoss looks great

Scouser

I have already done something similar to enable me to display different images or menus.

atilim

@ndoss thank you I've approved the pull request.

fawzma

Is there a scene editor in the works, or could someone write a plugin for cocosbuilder?

ilovdevs

A scene editor like cocosbuilder would be a really great implementation especially if it was free.

Cyberience

Yes a Native Version would be welcome, Unfortunately when I saw the onFrame event in the code, I decided to not use it. I would prefer as much control on what is repeatedly called. I would have most likely used a self terminating call back to do the loop rather than onFrame, as it stops when you don't need it any more.