Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340873 - Maximizing a part causes detached windows to go away
Summary: Maximizing a part causes detached windows to go away
Status: RESOLVED FIXED
Alias: None
Product: e4
Classification: Eclipse Project
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: 4.1 RC1   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 343298 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-03-24 11:24 EDT by Remy Suen CLA
Modified: 2011-05-04 16:23 EDT (History)
0 users

See Also:


Attachments
Make min/max behavior local to the window owning the stack (4.10 KB, patch)
2011-05-04 15:24 EDT, Eric Moffatt CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Remy Suen CLA 2011-03-24 11:24:40 EDT
I20110317-2200

1. Detach the 'Outline' view.
2. Maximize the part stack of the 'Package Explorer'.
3. The detached window for the 'Outline' view goes away!
Comment 1 Eric Moffatt CLA 2011-04-15 14:41:28 EDT
Good one...they don't really go away, they minimize to the trim.

The processing gathers up all the stacks for the window and minimizes them, looks like it's a bit too inclusive.
Comment 2 Remy Suen CLA 2011-04-29 08:05:10 EDT
This is still broken.
Comment 3 Eric Moffatt CLA 2011-05-04 15:24:44 EDT
Created attachment 194760 [details]
Make min/max behavior local to the window owning the stack


This not only fixes the reported scenario but also allows 'local' min/max behavior in detached windows.

The only funky behavior is that you are 'allowed' to minimize *all* the stacks. If you do you get an empty presentation area...if you don't like that state then restore one of the stacks.
Comment 4 Eric Moffatt CLA 2011-05-04 15:26:23 EDT
Committed in >20110504. Applied the patch.
Comment 5 Remy Suen CLA 2011-05-04 16:23:03 EDT
*** Bug 343298 has been marked as a duplicate of this bug. ***