Blog

I don’t have time to see if other, custom made SWC’s suffer the same fate, but the gist of it is, if you create a component and use say the “Button” component in your component. You then export your Button component for runtime sharing, and point the URL to the SWF name your compiling too, and then copy the main component to another SWF, he’ll work. Your Button in there will be importing from the Shared SWF.

…however, in publishing to both 6.0.65.0 and 7, while running in 7, once you add another tier, it doesn’t work. It has something to do with execution order, because if I manually drop the Button component on frame 1, and then the shared component who uses him on frame 2, the component will then work. This is not, however, how things are supposed to work. Because I can’t see behind the scenes of what initclip is doing, I’m not sure how to fix, but your supposed to just drop the component inside the component that needs it on a layer on frame 2. This isn’t working, however, so more study is warranted.

Oddly, I do not have this problem when utilizing the Central components in this way.

When creating new forms, the repitition of defining the form buttons and then attaching them in my init function gets old, quick. Until I update my Class Creator, here’s the next best thing using JSFL. You type in your component’s name (ex: cancel_pb), and click OK, then type in your class name (ex: mx.controls.Button), type in your class’s symbol name (ex: Button), and it’ll put the code you need in the Output window. If you don’t hit cancel (or leave a field blank), it’ll keep going. Save as a JSFL file, preferably in your Commands folder so you can re-use it.

Read on for code…