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: Sun, 7 Nov 2010 13:42:37 -0800
On Nov 7, 2010, at 1:29 PM, Seth Willits <email@hidden> wrote:
>
> Questions:
>
> a) Why does the first code snippet call the completion block "immediately"?
> b) If you assume A's answer is logical and correct, why does adding a completion block to the inner transaction affect the outer?
>
> Something seems wrong here.
Doesn't seem wrong to me. All 0 actions in your first example have completed when the transaction fires its completion handler.
It sounds like you're confusing transactions with animation groups.
--Kyle Sluder
(sent from the road)_______________________________________________
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