| Summary: | Maximizing a part causes detached windows to go away | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] e4 | Reporter: | Remy Suen <remy.suen> | ||||
| Component: | UI | Assignee: | Project Inbox <e4.ui-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | 4.1 RC1 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Remy Suen
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. This is still broken. 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.
Committed in >20110504. Applied the patch. *** Bug 343298 has been marked as a duplicate of this bug. *** |