User-agent: Mozilla Thunderbird 1.0+ (Windows/20050712)
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?