Re: CATransaction setCompletionBlock - Nested Transactions bug?
Re: CATransaction setCompletionBlock - Nested Transactions bug?
- Subject: Re: CATransaction setCompletionBlock - Nested Transactions bug?
- From: Kyle Sluder <email@hidden>
- Date: Mon, 8 Nov 2010 08:32:46 -0800
On Nov 8, 2010, at 8:26 AM, Matt Neuburg <email@hidden> wrote:
> On Sun, 7 Nov 2010 14:28:46 -0800, Kyle Sluder <email@hidden> said:
>
>> But transactions aren't actions. I'd even argue that putting this convenience method on CATransaction might have been a mistake.
>>
>
> It's not merely a convenience. We live in an age of blocks; we want the block-based approach to replace the old delegate-based approach. One is not merely a convenient form of the other; they are fundamentally different architectures. For true layer animation (as opposed to view animation) this *is* the block-based approach. Apple did not give a CAAnimation a completion block property, so you *have* to use CATransaction to get one. m.
As I mentioned before, we subclasses CAAnimationGroup to put the completion handler in the "right" (logically consistent) place.
--Kyle Sluder_______________________________________________
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