Comments on: OverwriteManager – control how (and if and when) tweens get overwritten

By: Jack

Jack — Mon, 09 Jan 2012 06:25:42 +0000

Jason, If all of the tweening properties have been overwritten, the tween is considered dead and the onComplete does not get called. This is by design – it is normally what most developers prefer.

By: Jason King

Jason King — Sun, 08 Jan 2012 23:55:48 +0000

If a new TweenMax overwrites all the tweens of an existing TweenMax and the old TweenMax has an OnComplete param, does the OnComplete get called?

By: Jack

Jack — Thu, 17 Feb 2011 08:13:34 +0000

Actually, outs, that depends on the LoaderContext you use when subloading. If you segregate the subloaded swf into its own ApplicationDomain, it won’t use the parent’s classes/settings like that. That’s not a bug or anything – it’s just how Flash works.

By: outs

outs — Wed, 16 Feb 2011 22:32:31 +0000

Hi Jack, I noticed that if you define a default overwriting mode for a parent swf, and load child swfs into it that have no default defined, the children swf will take on the parents default. Is this meant to be the correct behavior?

It caused a lot of headache as when I was developing and testing my child swf, everything was working fine, until I tested it from a load within my parent, and the child swf would no longer run some of my tweens. Googling “bug with child swfs and tweenmax” returns no results, until I eventually realized that a default overwrite setting will affect all the children swfs as well.

Thanks!!

By: viaria

viaria — Tue, 12 Oct 2010 13:43:43 +0000

jack,
i just love you man. you are the best man who makes his job well, i have ever seen yet.

By: RickM

RickM — Wed, 24 Feb 2010 19:41:39 +0000

Jack, this is awesome. I’ve been trying for days to get a slow, smooth zoom effect, and I did it in seconds thanks to you.

By: chris

chris — Sat, 04 Oct 2008 12:55:54 +0000

wow…
you did an amazing job thx.. i donate 20 dolars

By: jack

jack — Sat, 06 Sep 2008 21:29:24 +0000

Shadow_SB, if you’re careful with the way you write your code, feel free to use the NONE mode. You can always use the overwrite special property in individual tweens to accomplish whatever you want. You might also want to do some testing of your own to see how NONE compares with AUTO because you may be very surprised how efficient AUTO mode is. Frankly, I noticed very little difference even when running hundreds of tweens simultaneously. But if you want absolutely maximum performance, NONE or ALL is best. In most projects, however, given the almost imperceptible performance difference and increased convenience, I suspect most developers will appreciate AUTO. The nice thing is that OverwriteManager gives you lots of options.

By: Shadow_SB

Shadow_SB — Sat, 06 Sep 2008 21:08:49 +0000

Hi. I’m wondering about consequences of using NONE mode in cases that AUTO was made for… I suppose that this is not good idea but since NONE mode is more efficient it sounds seductive… Generally I don’t use thousands of simultenous tweens, but I do use TweenLite in cpu-stressful projects where performance matters

By: @ndre

@ndre — Fri, 05 Sep 2008 14:06:54 +0000

Ok, I mostly wanted to get confirmed that it worked the way I thought. I agree that the AUTO mode is the most intuitive, I remember being confused about the overwriting when I first started using TweenMax/Lite.

As long as I know about it, option 2) is no sweat at all.