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

Bug 322343

Summary: Resetting a perspective may preserve a view
Product: [Eclipse Project] e4 Reporter: Remy Suen <remy.suen>
Component: UIAssignee: Project Inbox <e4.ui-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: Lars.Vogel
Version: 1.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
StackRenderer patch v1 none

Description Remy Suen CLA 2010-08-11 08:36:20 EDT 
1. Ctrl+3 > Console
2. Window > Reset Perspective > OK
3. The 'Console' view is still at the bottom.

This can now be observed because parts are no longer necessarily discarded when a reset is performed (see bug 320671).
Comment 1 Remy Suen CLA 2010-08-11 09:02:51 EDT 
Created attachment 176335 [details]
StackRenderer patch v1

When the confirmation dialog closes, the OS sends an activation event back to the original focus control (the 'Console' view), this queues up a request to activate that stack. This request then gets processed after the reset is done which is why the 'Console' view ends up getting activated after the perspective has corrected itself.
Comment 2 Remy Suen CLA 2010-09-07 16:02:56 EDT 
While the original problem cannot be reproduced, I believe that the code still needs to be corrected.
Comment 3 Eclipse Genie CLA 2018-09-16 14:13:47 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Lars Vogel CLA 2018-09-16 14:21:20 EDT 
I don't think this bug is still relevant.