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

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.

By: jack

jack — Fri, 05 Sep 2008 13:59:13 +0000

@ndre, you are correct – since AUTO is now the default, there is a possibility that your old stuff won’t work exactly the same way. I weighed the decision to make the default mode AUTO and I realized backwards compatibility might be an issue at the default setting, but I decided to go with AUTO because:

1) It is the most intuitive and prevents confusion. I’ve gotten lots of “bug” reports that weren’t bugs at all – it was just that people expected auto overwriting and didn’t understand the old default behavior of overwriting ALL.

2) If you want to replicate the old default “ALL” mode, it’s super-easy. Simply call OverwriteManager.init(OverwriteManager.ALL); That’s it.

Basically, the benefits seemed to outweigh the risks. If anyone else wants to disagree or share their opinion, let me know. In the end, I think people expect (and are happiest with) the AUTO mode by default. Keep in mind you can control overwriting on an individual basis too – you don’t need to control it with the global OverwriteManager mode setting.

By: @ndre

@ndre — Fri, 05 Sep 2008 13:48:01 +0000

Looks like a very welcome addition. Only thing I’m a bit sceptic about after reading the post, is the default setting. If I understand it correctly, the ALL mode is the way that TweenMax (since this is the only class where it is included by default, my concern only applies here) used to work before?

Then, since the default mode is AUTO now, backwards compability is not 100%. If I replace the old classes with the new ones, it could potentially create unwanted results when recompiling my previous projects because properties that I expected to be overwritten when creating a new tween, isn’t…

Or did I misunderstand?

By: Chris Kelley

Chris Kelley — Fri, 05 Sep 2008 10:14:16 +0000

Outstanding – I just loaded up the site to double check the documentation on the old overwrite:false stuff and look what you’ve gone and done! Saved me a big headache, -again-.

Thanks, keep up the good work.
Chris

By: John Webber

John Webber — Tue, 02 Sep 2008 17:21:05 +0000

My fingers were sore from writing overwrite:false so often. Thanks buddy!

By: Og2t

Og2t — Tue, 02 Sep 2008 09:56:07 +0000

This is great Jack! I had some many headaches with overwriting different properties on the same object without stopping/resetting others – that should solve it all now! Thanks!