overwrite manager bug (maybe)

[viaria 0 Likes (Newbie)]

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

[viaria 0 Likes (Newbie)]

for detail,

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

[GreenSock 18,876 Likes (Superhero)]

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.

[viaria 0 Likes (Newbie)]

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.

[GreenSock 18,876 Likes (Superhero)]

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

If mode is 0, that means "none" or false - see the docs for details. http://www.greensock.com/overwritemanager/

[viaria 0 Likes (Newbie)]

thanks.