Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 307385 - LazyStackRenderer's activation listener causes undesired active part changes
Summary: LazyStackRenderer's activation listener causes undesired active part changes
Status: CLOSED DUPLICATE of bug 307199
Alias: None
Product: e4
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 1.0   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 307199
  Show dependency tree
 
Reported: 2010-03-29 09:09 EDT by Remy Suen CLA
Modified: 2010-03-30 15:50 EDT (History)
0 users

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 Remy Suen CLA 2010-03-29 09:09:05 EDT 
The LSR attaches an an SWT.Activate listener in hookControllerLogic(MUIElement). This can have fatal repercussions (besides the obvious that it downcasts to CTabFolder without a care in the world) as it arbitrarily activates the stack's selected element.

On win32 (and other platforms?), when an item is clicked on in the CTF, an activation event is fired. Consider the following scenario...

1. An editor is open with two views in a stack below.
2. View A is selected.
3. The editor is active.
4. The user selects view B to activate it.
5. SWT picks up this activation event and the LSR handles the stack's selected element, that is, view A. The selection event comes later and then view B is activated.

So we're getting two activation events for one action and we certainly do not want this to happen in this context. It is causing me problems with bug 307199.
Comment 1 Eric Moffatt CLA 2010-03-30 15:50:41 EDT 
I've marked this as a dup of 307199 since that's where the patch is...it also fixes the issues described there.

*** This bug has been marked as a duplicate of bug 307199 ***