When i see your videos i think "Angela Yu or Paul Hudson are the teacher i would want to have, but Sean it's the coworker any developer(jr or senior) want or must have in any working team"... Good content!
This is awesome! I had no idea this was possible and have been struggling trying to get UIView.Animate to do an animation very similar to the one you used here as your demo!
Thank you so very much, Sean for your hard work and effort. Your channel is is amazing source of knowledge when it comes to Swift or iOS development in general for newbies like myself. I also enjoy your informative podcasts while driving. Thank you for bringing so much for the community!
Sean you really are the best man I admire your hard work and dedication and thank you for sharing so much of your story, you are inspiring, This video is awesome I knew eventually you would get to UIViewPropertyAnimator thank you Sean!
Affine scaling multiplies whatever shape you have by the X and Y factors you specify. When you scale your shape to a value of zero, it basically means that you scaled your shape down to a point where it no longer exists in the 2D world (its X and Y lengths are zero). So when you try to scale it back up again, the computer no longer has any geometrical reference that describe your shape. It sort of lost memory of the original shape you had. As a result, it cannot scale it up anymore.
If the scale is zero, it tries to divide the currentTransform by 0 which equals to an error/infinity, that's why it causes problem and you should use 0.01 or 0.001, at least a number which is positive and bigger than 0.
Some thoughts, If the .xib is constrained based, maybe changing a constraint value is better. You might even have broken constraints. Animator holds closures of animations and closures hold self. I smell retain cycles! Maybe a capture list with self is required. 🙂 Nice example!
HI Sean thanks for the tutorial. Instead of using: self.planetImageView.frame.origin.y -= 400 I want to use self.planetImageView.transform = CGAffineTransform(translationX: 0, y: -400) Is this possible to do? When I try this it will work but it will not work with the delay and will also translate the image from below the screen to the top of the screen instead of starting in the middle of the screen and going up.
I'm not sure exactly what type of behavior you are looking for. But why not set the end animation value of that specific animation to the value you want it to stop at? For example, 80% opacity instead of 100%
@@seanallen Maybe off topic but i have problems with an image and labels. I use an image and using labels on top of it. I aligned them with constraints. Looking in the storyboard everything is fine but when i run the app via the simulator the image is misaligned with the labels. Do you know what the problem could be? THANKS!
Watch Next - iOS Take Home Project - Job Interview Practice - Free Preview - th-cam.com/video/MSIe2y6Fee8/w-d-xo.html
Good to see you back with a tutorial!
Thanks Thon 😀
When i see your videos i think "Angela Yu or Paul Hudson are the teacher i would want to have, but Sean it's the coworker any developer(jr or senior) want or must have in any working team"... Good content!
Thanks for those kind words, Felipe! I like to think I'm a good teammate 😀
The best free Swift content what you can find it on YT ! I love you man !
Thanks for the kind words 😀
This is awesome! I had no idea this was possible and have been struggling trying to get UIView.Animate to do an animation very similar to the one you used here as your demo!
Nice! Sounds like the video was very helpful then 😀
This is pretty cool stuff, Sean! Thanks for sharing. 👍
No problem Mark!
Thank you so very much, Sean for your hard work and effort. Your channel is is amazing source of knowledge when it comes to Swift or iOS development in general for newbies like myself. I also enjoy your informative podcasts while driving. Thank you for bringing so much for the community!
Nice video 👏👏 I am expecting more animations tutorials
Anything specific?
Very cool. To the point and no BS.
Glad you enjoy my teaching style 😀
Thanks Sean for this sweet sweet animation video.
Glad you liked it!
Sean you really are the best man I admire your hard work and dedication and thank you for sharing so much of your story, you are inspiring, This video is awesome I knew eventually you would get to UIViewPropertyAnimator thank you Sean!
I appreciate those kind words 😀. Happy to hear I could be of some inspiration.
Really well explained. Thanks for the video
Glad it was helpful, Diego!
Short and crisp ! Love it
Thanks Kalyani! Glad you enjoyed it.
Affine scaling multiplies whatever shape you have by the X and Y factors you specify.
When you scale your shape to a value of zero, it basically means that you scaled your shape down to a point where it no longer exists in the 2D world (its X and Y lengths are zero). So when you try to scale it back up again, the computer no longer has any geometrical reference that describe your shape. It sort of lost memory of the original shape you had. As a result, it cannot scale it up anymore.
As always simple and perfect you deserve more recognition 🤩 best content in youtube , "mobarak" 👌🏾👌🏾👌🏾
Thanks Mobarak 😀
If the scale is zero, it tries to divide the currentTransform by 0 which equals to an error/infinity, that's why it causes problem and you should use 0.01 or 0.001, at least a number which is positive and bigger than 0.
thanks sean, it is helpful as always
Happy to help 😀
Nice video Sean
Thanks SUDO!
Great tutorial 😊
Glad you liked it!
Wow 🤩
Swift animations!
P. S.
Great video Sean!
Thanks Caleb!
I am pretty sure you cannot set it to 0 because of division by zero in the transformation matrices used by CGAffineTransform.
Thanks. I learned something today 😀
Nice video 👏👏
Glad you liked it, Govind 😀
Great video
Thanks Siddharth. Glad you enjoyed it.
Some thoughts,
If the .xib is constrained based, maybe changing a constraint value is better. You might even have broken constraints.
Animator holds closures of animations and closures hold self. I smell retain cycles! Maybe a capture list with self is required. 🙂
Nice example!
It's not a .xib, but animating constraint is probably better. You don't need capture lists for the animation framework closures.
Nice!
Glad you liked it!
Good Tutorial
Thanks Sourish!
Thanks for helpful tutorial. Isn't self in closure cause a retain cycle? I think [weak self] is needed here, am I wrong?
Not in animation closures. There are certain types of closures that don't require it. GCD is another example.
HI Sean thanks for the tutorial. Instead of using:
self.planetImageView.frame.origin.y -= 400
I want to use self.planetImageView.transform = CGAffineTransform(translationX: 0, y: -400)
Is this possible to do? When I try this it will work but it will not work with the delay and will also translate the image from below the screen to the top of the screen instead of starting in the middle of the screen and going up.
Great content!. When your course gonna be released Sean?
Thanks Mohamed! Pre-sales will go live next week and I'm aiming to have the course available around the new year.
Hi sean! How to stop an animation after certain point. I want inverse of the delay factor. Any idea?
I'm not sure exactly what type of behavior you are looking for. But why not set the end animation value of that specific animation to the value you want it to stop at? For example, 80% opacity instead of 100%
any computer vision(matrix) process that multiply to 0 will be optimised (skipped), so probably thats why the transform didnt exist
Thanks. I learned something today 😀
Amazing 👍
Glad you liked it!
Great 👍
Glad you liked it 😀
Regarding your question about scaling by 0: stackoverflow.com/questions/25964224/cgaffinetransformscale-not-working-with-zero-scale
Thanks for sharing that, Mihai! I learned something today 😀
is it really that simple?👌 ofc like 👍
Glad you enjoyed it, Sasha!
you don't need to use a property animator to do this
I get you Xcode. Calm down🤣🤣🤣🤣
Great tutorial 👍🏻
Glad you liked it!
@@seanallen Maybe off topic but i have problems with an image and labels. I use an image and using labels on top of it. I aligned them with constraints. Looking in the storyboard everything is fine but when i run the app via the simulator the image is misaligned with the labels. Do you know what the problem could be? THANKS!