Another day, another post suggesting to use kCAFillModeForward and removedOnCompletion = NO. I’m looking at you, .
Conversation
To be fair, doesn’t recommend it but points out both ways in his article.
4
2
Oh, didn’t notice that. To add “why” to this “no”: even completed animations have overhead.
4
2
10
can I quote you on that (in upcoming a blog post)? That is: can I mention that the overhead exists and link to this tweet?
2
Here is the link. Fingers crossed that my understanding of the work the render sever does is correct. ronnqvi.st/multiple-anima
4
4
It so happens that right now, last-one-added wins, so if you add an absolute anim, then an additive anim, the latter wins.
1
2
is it foolish to rely on that behavior or should one simply not mix non-additive and additive anims with the same beginTime?
1
It would probably be too disruptive to change. To be safe: set additive beginTime to +1000, timeOffset to -1000. :)
1
Replying to
Eh, scratch that. That's just relying on another implementation detail. No better.
Replying to
btw, is the "animateWithDuration:0 uses parent context" behavior documented anywhere (46min into #236)? It looked odd to me.
1
1
Not very effectively. See docs for UIViewAnimationOptionOverrideInheritedDuration.
1
1
Show replies
Replying to
You can rely on anims on a layer running in beginTime order. If same beginTime, first one added goes first
2
3
Even if this wasn't described anywhere (can't remember) it's definitely relied on in places
1
2
Show replies