Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
This seems like a really basic question that has been surprisingly hard to find an answer to.
CABasicAnimations set up with “affineTransform” as the keypath haven’t worked for me, and in a bunch of places I’ve seen people eventually resorting to use CATransform3D instead with the “transform” keypath. Sure that’s a hint, but it would be good to have confirmation if “affineTransform” is meant to work or not?
Technically,
affineTransformis not a property of CALayer, and is documented as a “convenience method” wrapper around thetransformproperty, which is documented as animatable.It’s only really by objective-c’s implicit conversion of keypaths to selectors that it appears affineTransform behaves like a property when use (under most circumstances) in a keypath. However, the CA libraries are setup to observe only certain keypaths, and that’s not one of them 🙂