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
{{ message }}
This repository has been archived by the owner on Feb 19, 2021. It is now read-only.
I'm creating animations in Animate cc using the Snapsvg Animator. I used to go to Control>test which would open the test animation in my browser (Chrome), however it seems to have stopped allowing me to do this? Now if I click on test the Timeline panel flicks over to the Output panel and specifies the publish settings but it no longer opens a browser tab and plays the animation....despite test>in browser being ticked in the menu.
help on this would be much appreciated :)
Cheers.
The text was updated successfully, but these errors were encountered:
Thanks Pherting - I managed to solve the problem through the Adobe Animate cc forum. I think the preferences for the file had corrupted, so I copied all the layers out of that file into a new animate cc file, and that seemed to solve the problem.
FYI - I had been successfully testing the animation locally using the Chrome browser and have also been using it for testing successfully, since the problem corrected itself in the new file. But if the problem arises in the future I will flick over to Firefox and see if it works :)
Thanks again for your response :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there
I'm creating animations in Animate cc using the Snapsvg Animator. I used to go to Control>test which would open the test animation in my browser (Chrome), however it seems to have stopped allowing me to do this? Now if I click on test the Timeline panel flicks over to the Output panel and specifies the publish settings but it no longer opens a browser tab and plays the animation....despite test>in browser being ticked in the menu.
help on this would be much appreciated :)
Cheers.
The text was updated successfully, but these errors were encountered: