I am trying to instantiate and position a library asset
(MovieClip) programmatically. The classpath setting and import
directives, which work as expected for all other custom classes
(those which are not in the library), do not seem to affect library
symbols. It appears that the compiler works with its automatically
generated class for this (exported) symbol, while completely
ignoring my custom class for it. It is only when the custom class
resides in the root folder that it's respected; otherwise it's
ignored... This is not likely the result of some trivial error in
folder naming/hierarchy, or classpath/import settings/statements,
as I've meticulously ascertained this. But perhaps there is a
conceptual issue here that I miss. Although I've arrived at an
acceptable workaround to this problem, I'd love to understand the
reasons for this behaviour...
Many thanks for any comments!
if you have a class definition that's in your swfs classpath
that will be used before a class generated by flash. so, if you
have a class definition that's not being used by flash, it's not in
your swf's classpath.