Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369464 - [Compatibility] Maximizing a part when another part is maximized leads to lossage of original part
Summary: [Compatibility] Maximizing a part when another part is maximized leads to los...
Status: CLOSED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-23 19:30 EST by Brian de Alwis CLA
Modified: 2012-01-24 13:00 EST (History)
1 user (show)

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 Brian de Alwis CLA 2012-01-23 19:30:07 EST 
Version: 4.2.0
Build id: I20120110-2200

I was in the debugger, with the console view maximized (its stack, actually).  The application I was debugging hit a breakpoint, bringing up the Debug view.  I hit ^M, thinking it would either unmaximize the Console view and return me to the normal perspective.  It instead maximized the Debug view, which is ok too.  But upon unmaximizing the Debug view, the Console view's stack has disappeared.  Maximizing and unmaximizing the editors brought back the missing stack.
Comment 1 Remy Suen CLA 2012-01-24 12:08:40 EST 
Nothing in the logs, Brian?
Comment 2 Brian de Alwis CLA 2012-01-24 13:00:37 EST 
(In reply to comment #1)
> Nothing in the logs, Brian?

No, nothing.  And I can't seem to reproduce in I20120123-2200.  Marking as WORKSFORME.