What I believe is happening is this: In a normal situation starting a transition animation by removing the old view, adding the new one and then triggering CATransition works as expected. However, since in this two-part transition I'm starting a new fading transition inside the animationDidStop function (by removing the current, black view, and adding the final new view) the iPhone sometimes, for some reason, shows the replaced new view just before the new animation starts. This causes it to (sometimes) flash the final view very briefly on screen before starting the animation from the black view to the final view. This seems to happen only when I start an animation inside animationDidStop, but not in other more normal situations (such as on a button click callback function).
What I don't know is what to do about that. After the transition from the old view to the black view the animationDidStop function is called... and that's it. Nothing else that I know of gets called. I have no idea where else I could trigger the latter half of the transition (ie. from the black view to the final view).
|
