I think this is a must and if you compare with Cocos 2D, this is implemented since day zero: you can have any amount of transitions and timers going on (that are called actions and scheduled actions in Cocos), and you just call pause and resume, pseudocode example:
[Director pause] --> all transitions paused in their actual state, doesn’t matter what kind of transition or what the actual progress. Example: transition.to(img, {alpha = 0, time = 1000}).
It will pause in the middle of the alpha process and keep the time.
[Director resume] --> continue everything.
Actually in Corona you have to keep track of all the timing and transitions, and when un-pausing, you have to calculate and subtract the accumulated timing and create new transitions. That is too time consuming and lead to bugs. [import]uid: 10990 topic_id: 6198 reply_id: 306198[/import]