Can you please elaborate on the issue you are facing with Animate CC.
It will be good if you can share a video of the actual issue.
Using pre-compiled movieclips(swc-files) fails when reexporting because it says those definitions are already there, so eventually you have to compile those files twice all the time, once to fail because the definition already exists(breaking the existing swc file) , second time to actually compile the swc file.
You could delete the file EVERY TIME before compiling, but that takes longer.
A file saved in Animate CC, if you open it in an older flash (not all my colleagues have switched yet) doesn't complain, it's just impossible to build, somehow the class paths are screwed up.
Those are a few issues I noticed using Animate CC.
Not having the pin scripts feature is also a reason why most of my colleagues don't want to switch, but that's another discussion.
The pin script feature went away quite a while ago, so your colleagues are a few versions behind I guess.
There is a Clear Publishing Cache option, that can sometimes help with compile issues.
You can have multiple SWCs with the same class in them, and not have a problem. But, if you have the exact same class path in two SWCs, and the two do different things, it could lead to trouble. In cases like that in the past we have put the source for each SWC into its own subfolder. Then there are no clashes.
I you work with scripting heavy a lot, not pinning is really annoying, every time you focus on any other window, your code is gone and you can start looking it up in the list again, but ok nvm.
For the SWC, it seems that fla file was corrupted again, I fixed it by making a new fla copying the whole library , than copy all the settings and now it works. Probably a conversion issue.
I worked briefly with CS6, which had a fix corrupt file option, is there a possibility that this comes back or can be exposed somehow?
Working with big files, SWC's and classes seems to corrupt files from time to time, so if we could have a way to recover/fix the files, some kind of sanity check, that would be nice.
Can you please share the fla file compiling which you are facing the issue for us to investigate?
Also can you please share the Animate file opening which in CS6 causes issue for you?
"A file saved in Animate CC, if you open it in an older flash (not all my colleagues have switched yet) doesn't complain, it's just impossible to build, somehow the class paths are screwed up"
He tried it in cs5.5 not CS6.So that's probably not a good idea anyways.
I'm afraid , I'd have to send a whole bunch source of files to make those fla's buildable and would be against the nda I signed :-o.
I'll quickly see it I can recreate the issue.
No problem, I understand that Ken. A simplified file that repro the issue would be of great help to investigate & resolve this issue quickly.
I was able to make a file that gives the swc issue where it alternates
between building fine and giving warnings. Might already help.
Just copying the library over to a new fla fixes this.
I'll see if I have more time to look for that other issue.
can't seem to repro the issue my colleague had, strange, he probably had an unpatched flash cs5.5. I guess.