| Summary: | Minimizing all stacks in the contacts demo will cause it to shutdown | ||
|---|---|---|---|
| Product: | [Eclipse Project] e4 | Reporter: | Remy Suen <remy.suen> |
| Component: | UI | Assignee: | Project Inbox <e4.ui-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | critical | ||
| Priority: | P3 | CC: | c.keimel, tom.schindl |
| Version: | 1.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Remy Suen
In my opinion the Minimize should work like this. Assuming n > 1 PartStacks are active: If stack number n-1 gets minimized (meaning that n-2 stacks have been minimized already), then the status of the remaining "unminimized" stack should be set to MAXIMIZED. This way the result of minimizing n-1 stacks is the same as maximizing the remaining stack and the status of the workbench is always valid. If only one PartStack is active then Min/Max should be disabled. Looks like this bug has been fixed by the changes for bug 340873. Christoph, if you feel the points you raised are important please open individual bugs for them for each scenario, thank you for your input and for testing Eclipse 4! *** This bug has been marked as a duplicate of bug 340873 *** Have done so: Bug 345902 Bug 345904 |