Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359597 - [Perspectives] Reset perspective with views in shared area should reset views in all effected perspectives
Summary: [Perspectives] Reset perspective with views in shared area should reset views...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: PC Windows 7
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-30 14:33 EDT by Dean Roberts CLA
Modified: 2019-11-27 07:23 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dean Roberts CLA 2011-09-30 14:33:48 EDT
1) Open Java Perspective
2) Open Debug Perspective
3) Move outline view to shared area
4) Reset perspective
5) Switch to Java Perspective

Notice that the outline view is missing.

Whenever a view is moved OUT of a shared area (reset or dragging out) we should replace it in any perspective that we changed ourselves.

This is a lower priority defect that originally thought since it appears to only effects perspectives that are opened at the time the view is moved into the shared area.

In conversation with the team it was thought that one way to implement this is to use tags to mark views that are TBR=false as a result of a move to shared area.  Then we could use find to locate windows that need to be fixed when the view is moved out of the shared area.
Comment 1 Paul Elder CLA 2013-03-12 10:34:25 EDT
Found this in 4.3.0.I20130311-2000, too.
Comment 2 Lars Vogel CLA 2019-11-27 07:23:35 EST
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.

If the bug is still relevant, please remove the stalebug whiteboard tag.