Closed cassidyclawson closed 8 years ago
If this also happens if you don't use an animation or if you use a non-Pop animation, it's probably not an issue with Pop. In fact, Pop doesn't do anything more complex than setting the view or layer properties being animate. It might be good to investigate without animations at all, just by setting the layer properties.
It'll be hard for me to help debug further without a sample project to look at, unfortunately.
Thanks for the prompt reply @grp.
It does indeed happen with UIView animations. It does not happen without animations.
Do you have any intuition as to what could be happening under the hood and what I could start looking for?
Pop is just setting values over time. You could try setting values over time in your own code and see if you can isolate the issue that way? You should then be able to clearly see what changes when it doesn't work.
Thanks for the tip.
In case anyone finds this issue and faces a similar problem... this problem was caused by a method changing the frame of the animated object while the animation was in progress. I was able to find it by creating overrides for setCenter, setFrame and setBounds, adding breakpoints, and examining the stack to find a method I didn't know was interfering with the animated object.
As you can see in the gif above, I have two independent POP animations in the same view hierarchy.
The first animation is the caption swipe triggered by a touch gesture. The second is the recursive blooping of the "guess" button.
For some reason that I can't understand, the caption change animation can disrupt the recursive bloop animation, resulting in an unwanted change of size and origin of the button. This happens even if I use a basic UIView animation for the button bloop.
Thanks to everyone who has worked on this project. It really is cool.
Any ideas?
The swipe animation:
And the recursive bloop (this is called over and over using a timer)