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
Replying to
Oh, didn’t notice that. To add “why” to this “no”: even completed animations have overhead.
Replying to
Depending on the animation, it can be non-trivial. Ran into that hard doing UIMotionEffect.
1
2
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
Show replies
Replying to
that’s a reason I hadn’t even considered :) is the overhead just in keeping objects around?
2
No: “for each frame, apply this animation to the render tree”
1
Replying to
I'd say that an inconsistency between model and presentation is the big no. Isn't it?
1
Depends on your semantics, but certainly a big red flag.
1
Show replies
Replying to
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
let’s admit that the API is poorly done on this matter. It should be simpler to have an anim end “stick”
2
Show replies