I think the problem is that creatClassObject() wants a third param -- the depth for the child, which must be unique for each child. By not specifying it, you are effectively passing 'undefined' for the depth. This probably gets interpreted as 0 and you get a depth collision. Each successively created object blows away the previous one at depth 0.
- Gordon -----Original Message----- From: Scott Barnes [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 10:26 PM To: [email protected] Subject: [flexcoders] createClassObject bug? I've got a few components that extend mx.core.UIObject, and from a parent object i want to create two children objects (in that they all extend UIObject). ie: function parent() { this.child01 = this.createClassObject(com.SynergyFLEX.child01,"child1"); this.child02 = this.createClassObject(com.SynergyFLEX.child02,"child2"); } yet, it only creates the last one in the stack? in that if i debug or try and reference this.child01 it shows up null? If i use createChild() (forcing my parent container to now extend mx.core.View) it works fine. Yet that has me confused as doesn't createChild use createClassObject anyway? Wort's the G.O ? -- Regards, Scott Barnes http://www.mossyblog.com http://www.flexcoder.com (Coming Soon) Yahoo! Groups Links 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/
