Yes, there is no problem actually with this. Everything works ok. I just wanted to put my own CollapsablePanelGroup (manager that allows only one Panel in group to be in expanded state) class right before CollapsablePanel instances, like it's usually done with RadioButtonGroup and RadioButton
Of Sergey Kovalyov
Sent: Thursday, August 17, 2006 04:50
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Instantiating object in MXML
Hi All!
I have MyObject class that implements IMXMLObject interface:
package {
import mx.core.IMXMLObject;
public class MyObject
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?
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
: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Sergey Kovalyov
Sent: Monday, August 21, 2006 8:05
AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders]
Instantiating object in MXML
Yes, you
are right. But I implemented IMXMLObject interface. My class
Hi All!
I have MyObject class that implements IMXMLObject interface:
package {
import mx.core.IMXMLObject;
public class MyObject implements IMXMLObject {
public function initialized(document:Object, id:String):void {
}
}
6 matches
Mail list logo
