Because the object gets drawn before the next enterFrame event occurs. Thus, when a function updates the appearance of an object according to a transitioned value, there’s a small “tick” as the object is first updated by the transition and then updated by the function.
Specifically, I’m thinking of the Dusk Engine and camera scaling. When you use map:scale(1.05, 1.05) every frame and then directly after (before the next frame comes) use map.updateView() (which sets the map center to the correct place), everything’s fine. But if you use transition.to(map, {xScale = 2, yScale = 2}) and then map.updateView() in an enterFrame listener, the map “jitters” because the map is first scaled, and then, next frame, updated.
I have not posted it on the feedback; will do that directly.