Awesome! [import]uid: 30185 topic_id: 6548 reply_id: 23962[/import]
Excellent!
Now this is what I’m talking about.
Excellent out-of-the-box thinking x-pressive!
EDIT:
Recursive cleaning is no longer needed in your code. This was added to the SDK
http://developer.anscamobile.com/release/2011/318
Question though, why do you have to make the Scenes global? They can’t be local? [import]uid: 20703 topic_id: 6548 reply_id: 28686[/import]
@x-pressive.com … Thank you nice & clean code.
Can you help me to build clean approach for physics uses with screen transitions?
Especially when each scenes include there own physics and animations.
Thank you in advanced.
Admin6 [import]uid: 45018 topic_id: 6548 reply_id: 36506[/import]
Yes, this is fantastic just like their Particle Candy and Text Candy! I tested the texture memory in my code and it looks like this methods removes everything after each scene. And it’s so easy to work with multiple scenes.
To clean physics and animations like sprite sheets and bodies, just be sure to add then to a group (the code uses “sceneGroup”). If they are in sceneGroup they will be removed “automatically” by the code when you change scenes. (I’ve also made other groups with physics and animation and then simply added those groups to sceneGroup right before the change screen code.) Also be sure to remove all listeners and kill particles before changing scenes.
Do you have specific physics and animations that aren’t getting cleaned when sceneGroup is passed back to main? [import]uid: 40033 topic_id: 6548 reply_id: 36533[/import]