| Summary: | [Compatibility] [Intro] opening Welcome leave blank area | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Paul Webster <pwebster> |
| Component: | UI | Assignee: | Eric Moffatt <emoffatt> |
| Status: | VERIFIED FIXED | QA Contact: | Eric Moffatt <emoffatt> |
| Severity: | normal | ||
| Priority: | P3 | CC: | emoffatt, remy.suen |
| Version: | 4.2 | ||
| Target Milestone: | 4.2 M7 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Paul Webster
Yes, this is a tricky one...the problems start when there is more than one perspective open and you maximize a stack *outside* the perspective (seems like the second one doesn't even have to be rendered yet, I just tried a shutdown/restart with two persps open but hadn't clicked on the second one yet). It works with only one perspective open because the Cleanup Addon will correctly cascade the 'visible' state (so both the perspective and its stack go invisible once all the stacks have been minimized (i.e. visible -> false). What does maximizing a part outside the perspective mean ? Since it's outside the perspective it should stay maximized regardless of the current perspective would be my initial guess. Two possible solutions come to mind: 1) We minimize the perspective *stack* to the trim (the trim would then work like the perspective switcher, showing the open perspectives, clicking on one would switch to that perspective and show it in a 'fast' pane. This is fairly simple to implement but will beg the question of how to handle min/max in a minimized perspective (no trim on the 'fast' pane). 2) Minimize the stacks in *all* perspectives and let the trim manager take care of hiding / showing the trim elements on perspective switches. Note that we would also have to apply the minimization code to all newly opened perspectives as well. If anybody has other ideas please go ahead and post them here...I've set this defect for M5 since I suspect that it'll take that long to come up with the 'correct' answer... Fixed by the new 'minimize perspective stack' code... In I20120430-1800 PW |