Ah, I remember now, I never put visual children in my subclass, only code and faceless components.
Tracy ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Harui Sent: Wednesday, July 30, 2008 7:09 PM To: [email protected] Subject: RE: [flexcoders] Can we subclass Application yet? 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. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Josh McDonald Sent: Wednesday, July 30, 2008 3:17 PM To: [email protected] Subject: Re: [flexcoders] Can we subclass Application yet? I'm confused. You subclass Application every time you create a new Flex app, and in MXML. What problems are there to speak of? -Josh On Thu, Jul 31, 2008 at 6:08 AM, Alex Harui <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: You can certainly subclass Application via AS. Are you trying to do it in MXML? ________________________________ From: [email protected] <mailto:[email protected]> [mailto:[email protected] <mailto:[email protected]> ] On Behalf Of chigwell23 Sent: Wednesday, July 30, 2008 11:51 AM To: [email protected] <mailto:[email protected]> Subject: [flexcoders] Can we subclass Application yet? As far as I can tell the Flex2 problems with subclassing Application still exist in Flex3 i.e. bye-bye mxml components on parent class? Is this correct and has anybody worked around this? TIA, Mic. -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
