Community
Participate
Working Groups
1. File > New > Untitled Text File 2. Drag the 'Outline' view next to that new editor. 3. Window > Open Perspective > Debug 4. Notice that the view is separated and on the side and not as part of the editor stack. 5. Window > Open Perspective > Java 6. The 'Outline' view is missing. 7. Window > Show View > Outline 8. It does return appropriately.
(In reply to comment #0) > 8. It does return appropriately. Well, albeit in its original defined position and not in the editor stack.
This is a side-effect of being able to drag a view into the editor stack. I agree that the behaviour is a little surprising, but since the editor area is shared between all perspectives, we need to do *something* when you open a new perspective, or reset an existing perspective. Currently, because the code path for both these cases is the same, we err on the side of producing a perspective that looks exactly as expected, even if it effectively means removing views from other perspectives that were in the editor area.
I think we should consider the alternative approach of changing the perspective construction/reset behavior to determine if the view is already 'there' (in 'addView[Placeholder]'and to not create the MPlaceholder. Note that there are two possible ways for this to occur: 1) The View is in the Editor Area 2) The View is in a location *outside* the perspective stack. We intend to have the 'stickyRight' stack located directly under the MWindow so that the Help view(s) would be in the same spot regardless of the perspective.
No longer a problem. The 'Outline' view will stay in the shared area even after you switch to the 'Debug' perspective.
