Eclipse Community Forums: Standard Widget Toolkit (SWT) » Question regarding new Dispose Strategy in SWT 3.2

Help

Home

Home » Eclipse Projects » Standard Widget Toolkit (SWT) » Question regarding new Dispose Strategy in SWT 3.2

Show: Today's Messages :: Show Polls :: Message Navigator

Question regarding new Dispose Strategy in SWT 3.2 [message #459929]

Fri, 19 August 2005 00:24

Benjamin Pasero

Messages: 337
Registered: July 2009

Senior Member

Hi,

I noticed that in latest SWT 3.2 a lot of changes where made to the way
dispose() is working.

For example, in SWT 3.1 a Child received the dispose-event before the
Parent did. Now I am
getting a different result: Parent is getting the dispose-event first,
then the Child.

I think that is quite good and it leads me to this question:

Question: Is the new dispose strategy guaranteeing that when the parent
is receiving the dispose
event, _ALL_ Children of the Parent are not yet disposed and still fully
acessable, e.g. in order
to retrieve some state information for saving?

Thanks for the info,
Ben

Report message to a moderator

Re: Question regarding new Dispose Strategy in SWT 3.2 [message #460219 is a reply to message #459929]

Mon, 22 August 2005 23:27

Benjamin Pasero

Messages: 337
Registered: July 2009

Senior Member

Ping. Steve, VI :-) ?
> Hi,
>
> I noticed that in latest SWT 3.2 a lot of changes where made to the
> way dispose() is working.
>
> For example, in SWT 3.1 a Child received the dispose-event before the
> Parent did. Now I am
> getting a different result: Parent is getting the dispose-event first,
> then the Child.
>
> I think that is quite good and it leads me to this question:
>
> Question: Is the new dispose strategy guaranteeing that when the
> parent is receiving the dispose
> event, _ALL_ Children of the Parent are not yet disposed and still
> fully acessable, e.g. in order
> to retrieve some state information for saving?
>
> Thanks for the info,
> Ben

Report message to a moderator

Re: Question regarding new Dispose Strategy in SWT 3.2 [message #460391 is a reply to message #460219]

Wed, 24 August 2005 14:03

Steve Northover

Messages: 1636
Registered: July 2009

Senior Member

Yes (ping should have been SSQ and SN). The widget and all of its children
are full accessible. This fixes a bug report entered by Erich Gamma a very
long time ago. It was just too dangerous to make these change late in the
3.1 cycle so we did them early in 3.2.

"Benjamin Pasero" <bpasero@rssowl.org> wrote in message
news:dedjjf$7t2$1@news.eclipse.org...
> Ping. Steve, VI :-) ?
> > Hi,
> >
> > I noticed that in latest SWT 3.2 a lot of changes where made to the
> > way dispose() is working.
> >
> > For example, in SWT 3.1 a Child received the dispose-event before the
> > Parent did. Now I am
> > getting a different result: Parent is getting the dispose-event first,
> > then the Child.
> >
> > I think that is quite good and it leads me to this question:
> >
> > Question: Is the new dispose strategy guaranteeing that when the
> > parent is receiving the dispose
> > event, _ALL_ Children of the Parent are not yet disposed and still
> > fully acessable, e.g. in order
> > to retrieve some state information for saving?
> >
> > Thanks for the info,
> > Ben

Report message to a moderator

Re: Question regarding new Dispose Strategy in SWT 3.2 [message #460394 is a reply to message #460391]

Wed, 24 August 2005 14:20

Benjamin Pasero

Messages: 337
Registered: July 2009

Senior Member

Great to hear that!

Ben

> Yes (ping should have been SSQ and SN). The widget and all of its children
> are full accessible. This fixes a bug report entered by Erich Gamma a very
> long time ago. It was just too dangerous to make these change late in the
> 3.1 cycle so we did them early in 3.2.
>
> "Benjamin Pasero" <bpasero@rssowl.org> wrote in message
> news:dedjjf$7t2$1@news.eclipse.org...
>
>>Ping. Steve, VI :-) ?
>>
>>>Hi,
>>>
>>>I noticed that in latest SWT 3.2 a lot of changes where made to the
>>>way dispose() is working.
>>>
>>>For example, in SWT 3.1 a Child received the dispose-event before the
>>>Parent did. Now I am
>>>getting a different result: Parent is getting the dispose-event first,
>>>then the Child.
>>>
>>>I think that is quite good and it leads me to this question:
>>>
>>>Question: Is the new dispose strategy guaranteeing that when the
>>>parent is receiving the dispose
>>>event, _ALL_ Children of the Parent are not yet disposed and still
>>>fully acessable, e.g. in order
>>>to retrieve some state information for saving?
>>>
>>>Thanks for the info,
>>>Ben
>
>
>

Report message to a moderator

Previous Topic:	ToolBar isn't working
Next Topic:	SWT Layouts..

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 08:47:08 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter