On Jul 23, 2009, at 1:15 AM, David Duncan wrote:
On Jul 22, 2009, at 10:05 PM, Randall Meadows wrote:
Any idea why the drawing is screwing up for the 2nd animation? Are
the 2 different methods of animating messing up each other somehow
(even though I've removed the 1st animation)?
This is working as expected (for the default case at least). By
default a view (or layer) is not redraw when it is resized, but the
content is scaled. You want to change the contentMode on the UIView
if you want it to redraw (and understand that there is a performance
penalty for doing this).
That thought actually did occur to me, but I dismissed it for several
reasons:
1) The event that causes the "explosion" is another ball being placed
into the view by a click, and everything about this "catalyst" ball is
exactly the same as all the other balls, except it never gets the
initial movement animation applied to it. This catalyst ball
correctly animates its diameter change animation.
B) My interim fix was to remove the original ball view that was
moving, create a new ball view with the same properties as the old one
and insert it into the parent view, then apply the explosion
animation--essentially the same thing as the catalyst ball above.
Works great, no jaggies, perfect circle. Again, this object is the
same type, created the same way, as all the others, it just doesn't
have the initial animation applied to it.
That was enough to convince me that there was something else going on,
implicating the animation as being part of the problem. Regardless, I
changed the contentMode of the animated balls to
UIViewContentModeRedraw just to see what would happen, and now it
doesn't expand at all.
_______________________________________________
Cocoa-dev mailing list ([email protected])
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
