Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339237 - [DND] Maximized Editor stack loses its state after a perspective switch
Summary: [DND] Maximized Editor stack loses its state after a perspective switch
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-08 10:50 EST by Eric Moffatt CLA
Modified: 2019-11-14 02:22 EST (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 Eric Moffatt CLA 2011-03-08 10:50:04 EST 
Found in I20110307-2110 (3.7M6 candidate).

Start with both the Java and Debug perspectives open
In the Java perspective Maximize the Package Explorer
Switch to the debug perspective and maximize the Editor Area

Now switch between the perspectives...On the *second* switch the Debug's EA state will no longer show 'maximized'.

Clicking on it will change its state to maximized and then a second click will restore the minimized stacks.
Comment 1 Eric Moffatt CLA 2011-03-08 10:51:08 EST 
Tagging for M6, I'll check to see if this is an easy fix...if it's deep I'll change the target to M7.
Comment 2 Eric Moffatt CLA 2011-03-08 13:53:46 EST 
Changing milestone to M7..
Comment 3 Oleg Besedin CLA 2011-04-29 09:37:44 EDT 
The M7 is done.
Comment 4 Lars Vogel CLA 2019-11-14 02:22:05 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.