Which build are you using, and are you using memory profiling?
Early builds definitely had problems. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Firdosh Tangri Sent: Thursday, September 20, 2007 6:42 AM To: [email protected] Subject: [flexcomponents] Basic Button Component Test with Profiler Hey guys, I was playing around with the profiler in moxie and I was wondering if someone could explain this to me. <mx:Application xmlns:mx=" http://www.adobe.com/2006/mxml <http://www.adobe.com/2006/mxml> "> <mx:Button id="test" /> </mx:Application> Shows one instance of Button in profiler. Good :) <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml <http://www.adobe.com/2006/mxml> "> <mx:Button id="test" width="200" /> </mx:Application> Still one instance of Button in profiler. Good :) <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml <http://www.adobe.com/2006/mxml> "> <mx:Button id="test" width="200" height="300" /> </mx:Application> Now there are Three instances of the Button component ??? <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml <http://www.adobe.com/2006/mxml> "> <mx:Script> <![CDATA[ private function onClick(evt:MouseEvent):void{ test.parent.removeChild(test); } ]]> </mx:Script> <mx:Button id="test" width="200" height="300" alpha="0.75" x="20" y="30" click="onClick(event);"/> </mx:Application> Still there are Three instances of the Button component ??? thanks cheers firdosh
