enterFrame event callback vs transition.to timer callback

Getting Started Newbie Questions
#1

I have setup an event callback for the enterFrame event, and inside that callback, I also used a transition.to API call to do some display object movement, and at the end of the transition.to(), I have an onComplete callback. Somehow, it appears that the onComplete callback is not triggered. 

To my understanding, the enterFrame event is being called 30/60 times every second, I am wondering what would happen if my code block inside the enterFrame event callback takes longer time than the frame rate, would it be the possible cause that not firing the transition.to()'s onComplete callback? How would corona handle if the enterFrame event callback takes longer time than the supposed frame rate? What would happen ?

Thanks.

#2

It’s rather Corona restrict enterFrame to be called only 30 (or 60) times per second. If each frame will be rendered faster then Corona will wait the rest of 1/30th for frame. If it will take longer then your framerate will drop. Corona Sdk is not ‘threaded’. It won’t call next enterFrame listiner until all things are rendered. Also events and so on are probably handled at the beginning of each frame.
When it comes to transitions then they are handy because they are framerate independent. If you have object to move 10 px per frame then fr fluctuations will make it jitter - transition won’t.

#3

It’s rather Corona restrict enterFrame to be called only 30 (or 60) times per second. If each frame will be rendered faster then Corona will wait the rest of 1/30th for frame. If it will take longer then your framerate will drop. Corona Sdk is not ‘threaded’. It won’t call next enterFrame listiner until all things are rendered. Also events and so on are probably handled at the beginning of each frame.
When it comes to transitions then they are handy because they are framerate independent. If you have object to move 10 px per frame then fr fluctuations will make it jitter - transition won’t.