Thanks for your quick reply Oleg as always. I have been looking for ways to make this happen over the last few hours.
My latest brainwave (pathetic guess attempt) was a Document class called Main which looked something like this: public var itemRef:MovieClip = MovieClip(this.item); public var colorRef:MovieClip = MovieClip(itemRef.color); public var overlayRef:MovieClip = MovieClip(itemRef.overlay); I dont really understand the document class as Flash isnt really my working tool. However, i assumed this would work. If Main.as is a flas document class, then Main essentially becomes "root" ? In any case loadedSWF.itemRef = undefined. Usually we generate SWCs with Actionscript identifiers but since thats a compile time process?, and this is a runtime process, im a little confused. All of these swfs simply have: root -item --color --overlay I might just be best to stick to depths as long as im clear to explain that color must always be on the bottom depth. I still dont understand why names break however. Cheers, Clark. On 14 July 2010 12:50, Oleg Sivokon <olegsivo...@gmail.com> wrote: > > > Well, that wasn't a good idea from the start, as instance name isn't a > reliable identification (you can assign two identical names to different > instances and that will compile, while the second instance will not > be available). What I usually do in such case is: I prepare the class with > the fields it should have, give it to designer and explain hot to link their > library items to that class, and then when I compile, I use my own version > of that class with the functionality added, this way we (me and designer) > can work on the same class and I don't have problems using it in my project. > Ah, important to note, this approach requires that the designer turn off > the "automatically declare stage instances" in publish settings. > >
