As far as the UI goes, next to the lock and the eye, put a little running man icon, Click it and a “no” bar goes across it. So the transition will either run on load, or not.
The in code you just need to be able to trigger that created transition. You could make it similar to the sprite stuff, but I think under the hood it’s more of a transition, yes? So maybe add transition.play() and the obj you pass in is the obj with the GUI-created timeline stuff. That would also allow you to put an onComplete in that call.
For a timeline transition that auto runs, maybe have it trigger an event when it’s done, playcomplete – then I can add an event listener for that event if I want to do something when it’s finished.
Reading your reply again, yes, a clip API would be interesting. And it would open up the idea of “prefabs” to Corona. So instead of the timeline animations being an actual part of the scene, they are separate, but in the scene.
Or keep to just like it is GUI-wise, but allow the timeline animations to be called at any time with an API call (transition.play()?) – that might be cool. Set up different animations (even off screen) and then move them into place and trigger them when you want.
So much more potential than just an “auto run” when the scene loads.
As far as the UI goes, next to the lock and the eye, put a little running man icon, Click it and a “no” bar goes across it. So the transition will either run on load, or not.
The in code you just need to be able to trigger that created transition. You could make it similar to the sprite stuff, but I think under the hood it’s more of a transition, yes? So maybe add transition.play() and the obj you pass in is the obj with the GUI-created timeline stuff. That would also allow you to put an onComplete in that call.
For a timeline transition that auto runs, maybe have it trigger an event when it’s done, playcomplete – then I can add an event listener for that event if I want to do something when it’s finished.
Reading your reply again, yes, a clip API would be interesting. And it would open up the idea of “prefabs” to Corona. So instead of the timeline animations being an actual part of the scene, they are separate, but in the scene.
Or keep to just like it is GUI-wise, but allow the timeline animations to be called at any time with an API call (transition.play()?) – that might be cool. Set up different animations (even off screen) and then move them into place and trigger them when you want.
So much more potential than just an “auto run” when the scene loads.