Yes, you are right. But I implemented IMXMLObject interface. My class instantiates in the root of the component, but nowhere else. On the other hand native RadioButtonGroup that is also inherited from EventDispatcher, not UIComponent, could be instantiated even inside nested containers. Why so?
On 8/21/06, Daniel Thompson <[EMAIL PROTECTED]> wrote: > >From Programming ActionScript 3.0: > > "If you use Flex, you should know that Flex defines many component display > object classes, and these classes override the display list access methods of > the DisplayObjectContainer class. For example, the Container class of the > mx.core package overrides the addChild() method and other methods of the > DisplayObjectContainer class (which the Container class extends). In the case > of > the addChild() method, the class overrides the method in such a way that you > cannot add all types of display objects to a Container instance in Flex. The > overridden method, in this case, requires that the child object that you are > adding be a type of mx.core.UIComponent object." > > I'd be willing to bet that the MXML is calling addChild() and you haven't > extended UIComponent. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
