This content has been marked as final. Show 4 replies
dont name them that.
leotemp, that's a very smart(***) answer - but don't name them what? I read your earlier post of today: you might benefit by looking at Aral Balkan's Quick Start about skinning the components.
I have not seen anything in all the documentation about names to avoid in naming files. If there are restrictions on this, it would be nice to see a list of those names and the situations in which the restrictions apply. I would think renaming the file is not the first thing a programmer does when an unusual message shows up in the Problems window in FB.
If anyone has something to say about this, please do so. Cheers,
When compiling an MXML file, it first gets converted into an .as file. In your case, that generated file gets named transitions-generated.as. It gets erased afterwards unless you use the -keep compiler flag (ie. "use -keep to save"). I think what you're seeing here is just one of those things that slip through the cracks. The code is being generated in a way that's causing a naming conflict. You've probably bumped into a specific combination of class/file names that's doing this, so it's most likely a bug. So, in a way, the best advice is "don't name it that". :-) And perhaps forward the bug to Adobe.
Does there happen to be a function named "transitions" inside the "transitions.mxml"?