Eclipse Community Forums: Standard Widget Toolkit (SWT)

Home » Eclipse Projects » Standard Widget Toolkit (SWT) » To dispose or not to dispose

To dispose or not to dispose [message #447987]

Wed, 22 December 2004 10:41

Eclipse User

I have a scrolled composite and have done a setinput with a composite to scroll. When a certain selection event happens I create a new composite and set the input of the scrolled composite to that.
 
 Question is eclipse says that widgets created with a parent are disposed by the system when the parent is disposed. In my case the parent scrolled composite is not disposed and there could be a lot of selection events (circa 200) with say 20 widgets on each composite, does this mean there will be 4000 widgets hanging around until the scrolled composite is disposed.
 
 Will the scrolled composite dispose of the old input when a new setinput is done, is it safe for me to dispose of them or do I just leave them all hanging around until the scrolled composite is disposed when the view closes.

Re: To dispose or not to dispose [message #448006 is a reply to message #447987]

Thu, 23 December 2004 12:32

Eclipse User

Hi Phill,

In your scenario you could be looking at a lot of widgets hanging around,
because since they are all descendents of the ScrolledComposite, they will
not be auto-disposed until the ScrolledComposite is disposed. You may wish
to dispose() of a Composite once it loses its status as the
ScrolledComposite's current content, especially if you know that it will not
be needed again (ie.- you're not likely to use it again as an argument for
ScrolledComposite.setContent(...)). This should be safe to do.

Grant
_______________
<Phill_Perryman@Mitel.COM> wrote in message
news:cqc4jb$h4d$1@www.eclipse.org...

I have a scrolled composite and have done a setinput with a composite to
scroll. When a certain selection event happens I create a new composite and
set the input of the scrolled composite to that.

Question is eclipse says that widgets created with a parent are disposed by
the system when the parent is disposed. In my case the parent scrolled
composite is not disposed and there could be a lot of selection events
(circa 200) with say 20 widgets on each composite, does this mean there will
be 4000 widgets hanging around until the scrolled composite is disposed.

Will the scrolled composite dispose of the old input when a new setinput is
done, is it safe for me to dispose of them or do I just leave them all
hanging around until the scrolled composite is disposed when the view
closes.

Re: To dispose or not to dispose [message #448022 is a reply to message #448006]

Fri, 24 December 2004 06:31

Eclipse User

Thanks, I have added my own call to dispose after the set input. I have checked all the logs and could not find any errors about access to disposed widgets so it seems ok.
 
 Thanks for the help.

Re: To dispose or not to dispose [message #448145 is a reply to message #448022]

Mon, 03 January 2005 13:19

Eclipse User

Originally posted by: richkulp.us.NO_SPAM.ibm.com

You may want to try:

http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/plat form-swt-home/dev.html#tools

And use the SLEAK tool. This will tell you if you have any SWT resources
that aren't being disposed that should of been.

--
Thanks,
Rich Kulp

Previous Topic:	my java code together ve code
Next Topic:	should I dispose of a font when...

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jul 14 19:56:35 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter