This issue was fixed in Composer, the new scene manager (i.e. Storyboard 2.0). It will not be fixed in Storyboard. That manager is being deprecated in favor of its more modern sibling Composer. See: http://coronalabs.com/blog/2014/01/21/introducing-the-composer-api-plus-tutorial/
Rob
Am I safe in assuming we can use both Storyboard 1.0 and 2.0 in the same project simply using the appropriate requires? Would I get in trouble if I used both in the same scene. The only reason I would want to do this is make sure I’ve cleaned up all memory with my OLD storyboard 1.0 scene prior to starting my NEW storyboard 2.0 scene.
It’s possible to put multiple scenes in one .lua file. But unless you know what you’re doing, this would be fraught with problems. While you could possibly mix storyboard and composer scenes, i.e. call storyboard.gotoScene() to go to a storyboard scene and composer.gotoScene() to go to a Composer scene, I’m not sure why you would want to do this either.
Rob
Was this issue ever fixed?
This issue was fixed in Composer, the new scene manager (i.e. Storyboard 2.0). It will not be fixed in Storyboard. That manager is being deprecated in favor of its more modern sibling Composer. See: http://coronalabs.com/blog/2014/01/21/introducing-the-composer-api-plus-tutorial/
Rob
Am I safe in assuming we can use both Storyboard 1.0 and 2.0 in the same project simply using the appropriate requires? Would I get in trouble if I used both in the same scene. The only reason I would want to do this is make sure I’ve cleaned up all memory with my OLD storyboard 1.0 scene prior to starting my NEW storyboard 2.0 scene.
It’s possible to put multiple scenes in one .lua file. But unless you know what you’re doing, this would be fraught with problems. While you could possibly mix storyboard and composer scenes, i.e. call storyboard.gotoScene() to go to a storyboard scene and composer.gotoScene() to go to a Composer scene, I’m not sure why you would want to do this either.
Rob