You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
When a clip destroys itself via this.removeMovieClip(), the currently executing function immediately returns. Here is a minimal sample reproducing the issue: removeMovieClipReturn.zip
In Flash Player, "After this.removeMovieClip()" is never traced because the function immediately returns after removeMovieClip(). But in AwayFL, the function continues executing, so the trace appears.
Steps to reproduce the issue
Load the provided SWF in AwayFL
Click the blue rectangle
Observe the values traced in the console
Expected outcome
"After this.removeMovieClip()" should not be traced.
Actual outcome
"After this.removeMovieClip()" is traced.
The text was updated successfully, but these errors were encountered:
Description
When a clip destroys itself via
this.removeMovieClip()
, the currently executing function immediately returns. Here is a minimal sample reproducing the issue: removeMovieClipReturn.zipIn Flash Player, "After this.removeMovieClip()" is never traced because the function immediately returns after removeMovieClip(). But in AwayFL, the function continues executing, so the trace appears.
Steps to reproduce the issue
Expected outcome
"After this.removeMovieClip()" should not be traced.
Actual outcome
"After this.removeMovieClip()" is traced.
The text was updated successfully, but these errors were encountered: