import fl.transitions.Tween;
 import fl.transitions.easing.*;
 var myTween:Tween = new Tween(myObject, "x", Elastic.easeOut, 0, 300, 3, true);
 

Comments

No screen name said on May 5, 2007 at 7:14 AM :

Has anyone else experienced freezing with these tweens?

I figured at first they would freeze when the variable would loose scope, but now they just seem to break randomly.

KeenoChris said on Jun 7, 2007 at 8:05 AM :

I have this problem also, i am running 3 tweens on a MC (x, y and rotate). Sometimes its fine; others it just stops dead on the screen (the MOTION_FINISHED does not get called)

im not really doing much else

thegamemaker said on Jul 2, 2007 at 2:37 PM :

agreed TweenEvent.MOTION_FINISH occasionally does not fire and it drives me nuts.

No screen name said on Jul 2, 2007 at 9:37 PM :

Yeah i have this problem also.

djtechwriter said on Jul 5, 2007 at 4:29 PM :

If you store the Tween in a local variable (within a function), the variable may be garbage collected before the completion of the scripted motion. The Tween object needs to exist throughout the duration of the motion and should be declared in a larger scope.

No screen name said on Aug 3, 2007 at 6:46 AM :

How can I get access to the fl.transitions package. It is not accessible by default in my Eclipse environment after having installed the flex builder plug-in.

Robert Penner said on Aug 6, 2007 at 2:52 PM :

The fl.transitions package comes with Flash CS3.

No screen name said on Aug 24, 2007 at 12:29 AM :

> djtechwriter

i have my tween variable declared in class property (which is like global prop for that class). in function i fire new tweens: tween = new Tween(...) in "for" loop about 20 times. tweens crashes also, like other pip says.

any suggestions?

Robert Penner said on Aug 28, 2007 at 2:37 PM :

It sounds like you are creating 20 tweens, but only using one property. Each tween needs to be stored in its own property, so it can continue to exist.

ADI D said on Sep 17, 2007 at 2:01 AM :

maybe You wright... so U see any idea how to start and operate dynamic number of tweens (20-100)?

Robert Penner said on Sep 18, 2007 at 3:32 PM :

For a dynamic number of Tween objects, create an array and store them there.

JoshuaSullivan said on Oct 11, 2007 at 6:55 AM :

I've been banging my head against the "freezing tween" problem for a week now. Thank you for pointing out the garbage collection issue. Still, that shouldn't be happening if the tween has an event listener attached to it, should it?

swartz1999 said on Oct 11, 2007 at 5:54 PM :

Even if there is an event listener registered for an object, the object may be garbage collected if it is a local variable (within the scope of a function). To prevent this, declare the variable globally, as in the following:

var myTween:Tween;

function someFunction()
{
myTween = new Tween(myObject, "x", Elastic.easeOut, 0, 300, 3, true);
myTween.addEventListener(TweenEvent.MOTION_FINISH, listenerFunction);
// ...
}

No screen name said on Nov 1, 2007 at 9:14 AM :

So the only way around this problem is to set up (in my case) 300 tween vars, and then refer to each one in my loops? This is such a step backwards from 2.0.... I will be shopping for another Tween solution, because this new 3.0 method is obviously not built for handling multiple tweens easily.

intrinicity2 said on Nov 5, 2007 at 6:14 PM :

I too, am having the freezing problem and it is NOT fixed by declaring the Tween variable outside the scope of the calling function. About 20-ish iterations in to it and the tweens start failing to complete (not all, just most). A solution was suggested (by Robert Penner) to create many tween variables ), so that each iteration has its own, and store them in array.

I have struggled with this notion for a while now without success (generating dynamic variable names in AS3 is another task that's appears to have become more difficult than in its predecessor).

Could someone please post (and subsequently add to the documentation) a working example of how to generate multiple tweens rapidly, such that they complete.

Thanks

intrinicity2 said on Nov 5, 2007 at 6:31 PM :

As is often the case, you fire off a plea for help and then solve it within minutes of clicking submit.

Ignoring the details of the tween itself - this seemed to work fine:

this["aTween"+i] = new Tween(evt.target.loader, "alpha", Strong.easeOut, 0, 1, 2, true);
this["xTween"+i] = new Tween(evt.target.loader, "x", Regular.easeOut, evt.target.loader.x, numx*102+((stage.stageWidth-612)/2), 1.5, true);
this["yTween"+i] = new Tween(evt.target.loader, "y", Regular.easeIn, evt.target.loader.y, numy*34+((stage.stageHeight-136)/2), 1.5, true);

No tween variables defined elsewhere and no "var" in the statment... I'm actually a bit surprised that I could get away with it, AS3 being so strict on variable definition and all ...

nopaper said on Dec 3, 2007 at 10:18 AM :

It seems that a motionStop event is being dispatched even if the Tween has
normally finished (without an explicit call to tween.stop()). I found this when i
attached a listener to motionStop which removed all the listeners and
another one to motionFinished. Even if the tween would normally finish, the
listeners would all be removed before the motionFinished event is
dispatched.

No screen name said on Feb 26, 2008 at 1:07 PM :

Here is my 2 cents because I couldn't find a decent explanation anywhere. Please read and add your comments!

PROBLEM
Tweens finish early because they get randomly garbage collected


SOLUTION
Some form of reference that prevents garbage collection BUT does allow garbage collection when appropriate.

(Note the last part you don't want your Flash to clog up memory after executing for a long period of time)

Some people state declaring each tween globally (sometimes doesn't work?) others have made each tween a property of some global object. This is my solution for handling many tweens...


MY SOLUTION
//Anti Garbage Collection for Tweens
var antiGC:Dictionary = new Dictionary(false);

//Function with two tweens
function zoomIn(){
var scale:Number = diagram_mc.scaleX *1.12;

var xT:Tween = new Tween(diagram_mc, "scaleX",Strong.easeOut, diagram_mc.scaleX, scale, 5);
xT.addEventListener(TweenEvent.MOTION_FINISH, tweenFinished);
antiGC[xT] = xT;

var yT:Tween = new Tween(diagram_mc, "scaleY",Strong.easeOut, diagram_mc.scaleY, scale, 5);
yT.addEventListener(TweenEvent.MOTION_FINISH, tweenFinished);
antiGC[yT] = yT;


}

//Allows Garbage Collection
function tweenFinished(e:TweenEvent){

antiGC[e.currentTarget] = null; //GC Object
delete antiGC[e.currentTarget]; //GC Key

}

EXPLANATION

-Global dictionary with strong references will not be garbage collected
-Local tweens ok (e.g. in functions)
-...because tweens are stored in the dictionary
-EventListener triggers a global function to remove all references once finished
-...removing references allows garbage collection to do what it does

Note if you want your own MOTION_FINISH listener just remember to call the tweenFinished function



I'm no Flash or ActionScript expert, but I haven't seen anything tidier that is scalable and allows appropriate garbage collection.

Enjoy

OrbitalFlex said on Feb 27, 2008 at 2:16 PM :

I just ran across the issue of tweens stopping prematurely and would like to confirm swartz1999's solution. I had initially declared them local to a method within the object. I simply moved the tween variables out to become properties of the object itself. As long as the object is in play, so are it's tweens. All tweens now execute as expected.

ryanmagnon said on Apr 7, 2008 at 3:12 PM :

If you're still having a problem, you'll also check to make sure the object that the tween is a property of is not also being garbage collected due to scope or something else.

MythosVylok said on Apr 28, 2008 at 9:59 AM :

This worked for me:

TransitionManager.start(r_mc, {type:Zoom, direction:0, duration:1, easing: Strong.easeOut});

No screen name said on Jul 6, 2008 at 6:12 PM :

I had a similar problem with tweens freezing when using them to fade in an externalswf loader. Declaring the variable globally solved the problem and I haven't had a frozen fade since.