Closed GoogleCodeExporter closed 9 years ago
Its apparently not just opacity thats affected. Heres an altered example that
does height and x. The x works fine. The height on the other hard exhibits
seemingly the same behavior, which is to hide the object unto the animation is
complete, and then show it again.
Original comment by bduncan%...@gtempaccount.com
on 29 Jun 2010 at 12:35
Attachments:
The issue appears to be due to removing and readding the mask to the clipSprite
unnecessarily. I have made a fairly minor change to hold onto the node that we
are using as the basis for the clip path, and then check it when we go to apply
the clip path again during the next draw cycle. If its the same node that is
currently used as the clip, then we will not remove and readd a clone of the
node as the clip. The clone should be updated by the normal clone updating
process, so changes to the original should be picked up without needing to make
a new clone. I have attached another example. This one allows you to
dynamically change the clip path being used for the moving rectangle by
clicking in the white or yellow rect. This shows that the clip path is still
being updated when it needs to be, its just that the unneccesary removals and
readds have been eliminated. Note that the attached patch also has the diffs
from Issue 321 in it.
Original comment by bduncan%...@gtempaccount.com
on 29 Jun 2010 at 6:30
Attachments:
Fixed in r1209.
Thanks for the patch!
Original comment by grick23@gmail.com
on 3 Aug 2010 at 2:58
Original issue reported on code.google.com by
bduncan%...@gtempaccount.com
on 28 Jun 2010 at 7:24Attachments: