Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319441 - SWT.Deactivate not received with new Shell(s,SWT.SHELL_TRIM);
Summary: SWT.Deactivate not received with new Shell(s,SWT.SHELL_TRIM);
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-09 18:12 EDT by Lars Vogel CLA
Modified: 2014-02-28 07:00 EST (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Vogel CLA 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 CLA 2010-07-10 13:15:01 EDT 
Shouldn't we be sending this off to SWT?
Comment 2 Lars Vogel CLA 2014-02-28 07:00:39 EST 
I don't remember why this was important, closing as INVALID