Roger, > ...I'm wondering "Why is he trying to subclass inside Flash MX?"
Well, I was following the examples for extending components. I can see why visual components are extended using Flash MX because you define the visual assets that you will be extending. So, following the same steps, I dragged the mx.containers.HBox from the components list and placed it onto an "assets" timeline (frame 2) in my component symbol, just as you would if, for example, you were extending a Button. But I did think it odd that I would have to follow the same process for extending a container class, which has no visual assets. > Failing all that, why not just define your HBox subclass as an > ActionScript component in Flex? After playing around some more, this is the solution I came up with too. At this point, all I have is an AS file being consumed by the MXML file. Is there any point in trying to package this AS, and any future AS files, into an SWC file? And how would I do that? > I can't really imagine how a SWC is getting written for a subclass > of HBox that doesn't have the base classes for the HBox included. > But maybe it is in there! Please open MyContainer.swc inside > WinZip and look at the Catalog.xml file. Is there a > __Packages.mx.containers.HBox? What's the timestamp? Does it > match the timestamp in the catalog for mx.swc? FWIW, I did check my current SWC: <asset id="__Packages.mx.containers.HBox" modified="1079077593"> <exportAfter id="__Packages.mx.containers.Box"/> </asset> <asset id="mx.containers.HBox" modified="1079613635"> <include id="mx.containers.Box"/> <exportAfter id="__Packages.mx.containers.HBox"/> </asset> As you can see, yes the correct packages are there but no the timestamps do not match. =Kevin=
