Makes sense, since you're overriding Container._childDescriptors anyway. But why on earth would you *want* to do this?
-Josh On Thu, Jul 31, 2008 at 9:08 AM, Alex Harui <[EMAIL PROTECTED]> wrote: > Any attempt to subclass an MXML Component based on a container to add > other children to it usually results in some issue or another, usually that > thing about "children have already been defined", so you can't really make a > template app in MXML where it has some default components and use that as > the top tag in another app. There are some workarounds, but it isn't very > smooth. > > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
