Skip to main content
P
PippoApps
Inspiring
July 14, 2017
Answered

BUG: Impossible to work with Components in Animate CC 2017.5 - 16.5.1.104

  • July 14, 2017
  • 1 reply
  • 658 views

1 - Copy a component in one layer

2 - Paste it in another layer

Result: NOTHIG HAPPENS

1 - Copy a component in a document library

2 - Paste it in another document library

Result: only folders of component assets get created in new library, none of the assets appears.

1 - Drag a component from library to stage in an empty layer

Result: screen flickers, nothing happens. Layer stays empty.

The only way is create a movieclip with the component inside, drag it to stage, then brak apart, and use the component.

You can try in attached fla (if I manage to attach it), to copy from one layer to another.

THIS IS NOT THE FIRST TIME A NEW RELEASE BREAKS COMPONENTS USAGE.

PLEASE CHECK COMPONENTS USAGE BEFORE RELEASING NEW VERSIONS.

This topic has been closed for replies.
Correct answer The Noble Robot

Thank you for looking into this, but for crying out loud, this was a really frustrating oversight. I just wasted two days "debugging" this issue before finding this thread and realizing that it wasn't a corrupted FLA, or bad compiler settings, or something else with my project.

However, I (just now) discovered an odd workaround: For your custom Component, go to the Component Definition settings window and select the "display in Components panel" option. This seems to "elevate" your custom Component to "official" status, and it suddenly works again.

1 reply

P
PippoAppsAuthor
Inspiring
July 14, 2017

Download test fla here: http://www.pippoapps.com/_demo/animateBug/ComponentsCopyPasteBug.fla

Mohanaraj
Adobe Employee
Mohanaraj
Adobe Employee
July 14, 2017

Hi - Sorry for the inconvenience. Copy paste workflows for in-built components are working fine but we could repro the issue with the custom component in the file provided. We are investigating it.

Thanks!

Mohan

P
PippoAppsAuthor
Inspiring
July 16, 2017

Thank you for looking into this, but for crying out loud, this was a really frustrating oversight. I just wasted two days "debugging" this issue before finding this thread and realizing that it wasn't a corrupted FLA, or bad compiler settings, or something else with my project.

However, I (just now) discovered an odd workaround: For your custom Component, go to the Component Definition settings window and select the "display in Components panel" option. This seems to "elevate" your custom Component to "official" status, and it suddenly works again.


Ah great idea another workaround I found is to drag any movieclip, and swap it with your custom component. After swapping it stays there. Apparently it bypasses censorship eheh

A few versions ago, a new release just didn't save custom components. You could use them, but then in the saved version they weren't there. This drove nuts me and imagine the rest of the team collaborating on git.

Apparently we are not many working with custom components. But they are at the core of my framework, incredibly useful tu build interfaces quickly.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices