On Sat, Mar 6, 2010 at 3:08 PM, Steven Degutis <steven.degu...@gmail.com> wrote: > 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...
Isn't this an artifact of dealing with the model layer? I would expect that as far as my code is concerned, the sublayer is removed from its parent layer immediately, because I'm only dealing with the model layer tree, not the presentation layer tree. --Kyle Sluder _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
