> Does that mean that the original event was "queued" for one or more
> reasons and when it got processed the attached widget was already
> disposed ?
Yes, SWT sends some of its events like this in order to improve event
ordering consistency between its platforms. However even a queued event
will not be sent for a disposed widget. I assume that you're receiving
this event from a non-disposed widget, and are then trying to access
another widget that has just become disposed? What type of event are
you receiving? Widget.isDisposed() checks are sometimes needed, but it
should be clear to see why the widget you want to use is disposed (don't
just fall back on an added Widget.isDisposed()). If this varies between
platforms (does it?) then you could be seeing an swt platform inconsistency.