Re: CATransaction setCompletionBlock - Nested Transactions bug?
Re: CATransaction setCompletionBlock - Nested Transactions bug?
- Subject: Re: CATransaction setCompletionBlock - Nested Transactions bug?
- From: Seth Willits <email@hidden>
- Date: Sun, 7 Nov 2010 16:35:37 -0800
On Nov 7, 2010, at 2:28 PM, Kyle Sluder wrote:
> If nested transactions counted, you could never use this method safely and call into framework or other code. Any transactions that other code creates would screw up your own timing, even if the animations were entirely unrelated to your own.
I don't see how it'd make anything unsafe. Waiting on the timing of all nested animations is the point of the completion block. Apple agrees, given that in my second example it does that as I expect.
--
Seth Willits
_______________________________________________
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