Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 319441

Summary:	SWT.Deactivate not received with new Shell(s,SWT.SHELL_TRIM);
Product:	[Eclipse Project] Platform	Reporter:	Lars Vogel <Lars.Vogel>
Component:	SWT	Assignee:	Platform-SWT-Inbox <platform-swt-inbox>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	P3	CC:	bokowski, Lars.Vogel, ob1.eclipse, pwebster, remy.suen, tom.schindl
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Lars Vogel

2010-07-09 18:12:00 EDT

This is a follow up from https://bugs.eclipse.org/bugs/show_bug.cgi?id=319250.

When using:

--------------
new Shell(currentActiveShell.getDisplay(),SWT.SHELL_TRIM);
----------------
You *DON'T* get a Deactivation-Event when the shell closes.

Whereas you get one if you open a shell like this:
----------------
new Shell(currentActiveShell,SWT.SHELL_TRIM);
----------------

Probably some SWT-Experts can explain to us why. For us this means listening to
SWT.Deactivate is probably not enough because we can't force the user to create
a shell as the parent of another one.

As suggested to Tom Schindl I open this follow bug. https://bugs.eclipse.org/bugs/show_bug.cgi?id=319250 was closed as Tom adjusted his implementation.

Comment 1 Remy Suen

2010-07-10 13:15:01 EDT

Shouldn't we be sending this off to SWT?

Comment 2 Lars Vogel

2014-02-28 07:00:39 EST

I don't remember why this was important, closing as INVALID