I'm experiencing some weirdness when using the Flex Kit for CS3. I have a
MovieClip I'm exporting to a .swc (for Flex) as a UIMovieClip called
"AnimationPanel." I'm defining the class in a separate AnimationPanel.as
file with a class definition of:
public class AnimationPanel extends UIMovieClip
I've already used the "Make Flex Component" command on the symbol in the
library and it reads the class correctly. There are are 10 child movieclips
within this main UIMovieClip timeline I want to access from the
AnimationPanel.as class. When I tried to compile, the compiler complained
that it didn't know what these movieclip references were. So I added member
definitions in the AnimationPanel.as file...
private var animHC:MovieClip
private var animCHL:MovieClip
... and so on.
That worked for all but two, which the compiler still said it didn't know
what they were. (I checked spelling and the instance name field for these
two.) Why thse two? Dunno.
This is the funny part: I did one thing...I moved the layer that the
supposedly missing movieclip was on. Suddenly, the compiler decided that "a
conflict exists with definition [movieclip name] in namespace internal"* for
every child movieclip l had defined*! So now it didn't want *any *definitions
in the class...they were being picked up automatically from inside the
movieclip. So now I took out all the member definitions and it worked fine.
Ehh...
I gues this is my ignorance of how the compiler works with movieclips, their
members, and classes that define the movieclips. Are you supposed to define
child movieclips that exist on the timeline in the .as class when
subclassing UIMovieClip? Does anybody know where to go to learn more about
how the compiler works in this case? Eveyrthing's working now but I'd like
to know what's going on.
Thanks in advance for any help!
Daniel
Santa Cruz, CA
