2 people found this helpful
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.
1 person found this helpful
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.