Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Newly created MovieClip (defined by AnimateCC script) is unstoppable #779

Open
tjutasi opened this issue Jun 23, 2016 · 6 comments
Open

Comments

@tjutasi
Copy link

tjutasi commented Jun 23, 2016

Since AnimateCC publish everything as MovieClip the newly created MovieClips is unstoppable right after the creation, could stop only some time later. (FlashCC published the same objects as Container, and there was no problem to stop them) for example:

this.BG_holder=new lib.abui_BackGround();
this.BG_holder.title.gotoAndStop(0);

and this.BG_holder.title still loops it's timeline. When I click a button which call

this.BG_holder.title.gotoAndStop(0)
  • it's stopped at frame 0.

We can't use AnimateCC because of this bug.

@ggVGc
Copy link

ggVGc commented Jun 25, 2016

Yeah, I am pretty sure this is a bug. I sent a PR regarding it a few days ago, #778

@lannymcnie
Copy link
Member

We are aware of this bug, and are hoping to have a solution for it in a future release. In the mean time, I believe forcing an update on the parent timeline can resolve this:

this.BG_holder=new lib.abui_BackGround();
this.BG_holder.gotoAndStop(0); // Force update
this.BG_holder.title.gotoAndStop(0);

@tjutasi
Copy link
Author

tjutasi commented Feb 9, 2017

I don't see what this.BG_holder.title should be here, and there is no 'parent timeline'.

@lannymcnie
Copy link
Member

This is based on your code. Basically, you have to force this.BG_holder (the parent timeline of the "title" instance) to update first, and then you can call title.gotoAndStop(0).

@Trost123
Copy link

Trost123 commented May 6, 2017

+1 to this.
Is there a chance to bring Container class back to Animate CC, so we can get rid of this bug?

@lannymcnie
Copy link
Member

That is the hope. This was a change by Adobe, so we are working with them to resolve. Cheers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants