Is kCAOnOrderOut too good to be true?
Is kCAOnOrderOut too good to be true?
- Subject: Is kCAOnOrderOut too good to be true?
- From: Steven Degutis <email@hidden>
- Date: Sat, 6 Mar 2010 18:08:11 -0500
Hi all,
I've been reading the docs for Core Animation, specifically about
layer-actions, and it mentions a constant called kCAOnOrderOut which is
supposedly called when your layer is removed from its superlayer (or
hidden). However, if it's removed from superlayer, the animation returned
for the kCAOnOrderOut event is apparently ignored, because the layer is
removed immediately, instead of when the animation finishes. The docs
practically declare that this is meant for animations. So, what gives? Is
this too good to be true? Do I need to use the workaround of adding the
animation, and in the didStop delegate, removing the layer myself? Code
would be so much cleaner if just calling -removeFromSuperlayer would invoke
the animation for me and then remove it itself...
-Steven
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden