onEnterFrame (MovieClip.onEnterFrame handler) -- Version 8

Invoked repeatedly at the frame rate of the SWF file. The function that you assign to the onEnterFrame event handler is processed before any other ActionScript code that is attached to the affected frames.

You must define a function that executes when the event handler is invoked. You can define the function on the timeline or in a class file that extends the MovieClip class or that is linked to a symbol in the library.

Example

The following example defines a function for the onEnterFrame event handler that sends a trace() action to the Output panel:

Comments

Gareth Gibson said on Feb 14, 2006 at 12:03 PM :

there must be a way of removing this as well?

Steve431 said on Feb 21, 2006 at 1:33 AM :

Yes, you can stop the onEnterFrame event with the delete function

mc.onEnterFrame = function()
{
if(mc._alpha < 100) {
mc._alpha += mc._alpha+1;
}

else
{
delete this.onEnterFrame;
trace("done");
}

}

You will notice that once the onEnterFrame event has finished 'done' will only appear once in the output window, if you hadn't deleted the event you would get continious string of 'done's.

Space2Burn said on Feb 21, 2006 at 10:32 AM :

In the past I have used:

my_mc.onEnterFrame = null;

... once the condition is met.

I doubt this is the proper way to do it, but it does shut it down.

Bill O said on May 17, 2006 at 2:46 PM :

I have also used:

mc.onEnterFrame=undefined;

but I like the delete method better.

rghome said on May 8, 2007 at 7:01 AM :

Can the order of onEnterFrame calls for different MovieClips be controlled or determined? In particular, it would be useful to ensure that a parent MovieClip onEnterFrame call is executed before that of a child clip; however, this does not seem to be the case.

lumpenprole said on Jun 7, 2007 at 10:50 AM :

It needs to made clear that the function in question will fire once after being deleted. This is counter-intuitive.