Re: [flexcoders] Re: Tools for listing objects

Thu, 27 Jul 2006 07:43:15 -0700

Laszlo had a pretty nice debug window that you could embed in the  client side swf. the debug window could provide complete introspection into the client side views. anything similar available for flex or is anything planned such as this?

On 7/27/06, Matt Chotin <[EMAIL PROTECTED]> wrote:

We've been thinking about trying to expose a tool that would give you an accurate count of objects but it's not something near-term.  If the object is not on the display list (not in raw children) but is still sticking around then you clearly have a reference to it somewhere.  Typically it would be an event listener that wasn't added with a weak key or something that is referred to by another class that is on the display list.  Unfortunately I don't have a good technique for finding those L

 

From: [EMAIL PROTECTED]ups.com [mailto: flexcoders@yahoogroups.com] On Behalf Of jeff tapper
Sent: Wednesday, July 26, 2006 12:47 PM
To: [EMAIL PROTECTED]ups.com
Subject: [flexcoders] Re: Tools for listing objects

 

Darn, I've been able to prove to myself that the object can still
exist in memory but not be in the rawchildren. How can i get a
handle on these orphans? Do I need to resort to creating a
Dictionary Object with weak keys, and store an reference of every
object created in there? Is there a more elegant solution?

--- In [email protected], "jeff tapper" <[EMAIL PROTECTED]> wrote:
>
> Matt-
>
> Your solutions didnt work for me, I suspect its because all the
> children we create/destroy in this app are done via the popup
> manager. Regardless how many children we created that way, I'm
> always finding that:
> this.childDescriptors.toString();
> var o:Object = ObjectUtil.getClassInfo(Application.application);
> trace(ObjectUtil.toString(o));
> and Application.application.getChildren().toString() return the
same
> things, whether there is 0 or 100 windows open. So far, the best
> I've found for our needs is:
>
> var childList:IChildList = this.systemManager.rawChildren;
> for(var i:int=0;i<childList.numChildren;i++){
> trace(childList.getChildAt(i));
> }
>
> My fear is that there may be "orphans," windows which have been
> removed from the display list but which are still active in
memory.
> Any idea how to check on that?
>
> --- In [email protected], "Matt Horn" <mhorn@> wrote:
> >
> > I don't know about those tools you mention, but some ideas for
> listing
> > available objects:
> >
> > 1) trace(this.childDescriptors.toString());
> >
> > 2) var o:Object = ObjectUtil.getClassInfo
(Application.application);
> > trace(ObjectUtil.toString(o));
> >
> > 3) trace(Application.application.getChildren().toString());
> >
> > hth,
> >
> > matt horn
> > flex docs
> >
> > > -----Original Message-----
> > > From: [email protected]
> > > [mailto:[email protected]] On Behalf Of jeff tapper
> > > Sent: Wednesday, July 26, 2006 10:22 AM
> > > To: [email protected]
> > > Subject: [flexcoders] Tools for listing objects
> > >
> > > Does any one know of a tool like "OptimizeIt!" for java, or
> > > like "List Objects" in Flash Studio for finding all objects
> > > currently in existance? We are looking to verify that we have
> > > truely cleaned up objects no longer in use, and released them
> > > to the GC, but without a tool like this, we cant tell what
> > > exists and what doesnt. Does anyone have any tips?
> > >
> > >
> > >
> > >
> > >
> >
>


__._,_.___

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice

YAHOO! GROUPS LINKS



__,_._,___

Reply via email to