Community
Participate
Working Groups
1) Open debug perspective and activate the breakpoints view 2) Open the java perspective and activate the packages explorer. 3) Switch back to the debug perspective. Note that the editorpane is activated instead of the breakpoints view. 4) Click on breakpoints view again 5) Switch back to java perspective Note that the editorpane is activated again instead of package explorer.
I THINK this is the intended behavior. If the active part doesn't exist in the new perspective then the editor area becomes the new part.
It's actually random, it's not always the editor area.
Whatever parts the two perspectives have in common (in this case the editorpane was first), the MRU part from that intersection gets activated. It might be the console or the search view or something else. IMO, stacked perspectives should behave like separate windows, the only possible exception being when the currently active part is visible in the new perspective.
I think that is how it's designed ... it tries to activate the current active part ... if that part is closed because of the perspective, it will try to find the MRU part that is visible in the perpspective. There might be some revisting of this algorithm, see bug 91487 PW
> part ... if that part is closed because of the perspective, it will try to find > the MRU part that is visible in the perpspective. Except it doesn't do that. It finds the MRU part which was ALSO present in the previous perspective. This could be potentially any part so the behavior is not useful. What is needed is better management of the global MRU list or separate lists for each perspective. See also bug 89910.
Is this still a problem in 3.3? PW
yes
This is fixed in Eclipse Mars.
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.
