Jump to content


overwrite manager bug (maybe)

Moderator Tag

Recommended Posts

hi jack,

just try this line of code, there can be a bug in overwritemanager, it took my 2 weeks to catch.


import com.greensock.*;
import com.greensock.easing.*;

trace("before:", OverwriteManager.mode); // returns 0 // 2 is default -> http://www.greensock.com/overwritemanager/

TweenMax.to(box, .5, {x:100}); // just a simple tween.

trace("after:", OverwriteManager.mode);  //returns 2

Link to comment
Share on other sites

for detail,

i made a timelinemax and made a couple of tween in it that is where things did not work as expected.

Link to comment
Share on other sites

Nope, that's not a bug at all. As indicated in the docs, TweenMax and TimelineLite/Max automatically kick the default OverwriteManager mode to AUTO (2). In your example, you traced the mode BEFORE Flash instantiated the TweenMax class which is why it wasn't in AUTO mode yet at that point, but once you called TweenMax, it automatically did its thing and made the mode AUTO.


When you say that "things didn't work as expected", could you clarify what you mean? A very simple FLA that demonstrates the problem would be very helpful.

Link to comment
Share on other sites

i made a simple example but it works as expected.

i could not find any bug again, i guess it is my stupid mistake somewhere in code.

do you never make mistakes man? sorry for taking your time.


one question:

first trace returns 0, does that mean false or index 0.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.