Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345904 - MinMaxAddon: Minimizing of all stacks is not efficiently handled
Summary: MinMaxAddon: Minimizing of all stacks is not efficiently handled
Status: CLOSED WONTFIX
Alias: None
Product: e4
Classification: Eclipse Project
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: All Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-16 06:03 EDT by Christoph Keimel CLA
Modified: 2019-09-04 03:13 EDT (History)
0 users

See Also:

Attachments
testcase project (25.47 KB, application/zip)
2011-05-16 06:04 EDT, Christoph Keimel CLA 		no flags Details
Demonstration of the effect (PDF) (63.02 KB, application/pdf)
2011-05-16 06:04 EDT, Christoph Keimel CLA 		no flags Details
View All 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 Christoph Keimel CLA 2011-05-16 06:03:58 EDT 
Build Identifier: I20110501-0200

Feature request: When minimzing all stacks, the is no more information to be seen. When the next to last stack of the current view is minimized, the application should automatically transfer the mode of the last remaining stack to “maximized”. 

Reproducible: Always

Steps to Reproduce:
1. Create an application with 2 stacks
2. Minimize stack nr. 1
3. Minimize stack nr. 2
=> The window area is blank
Comment 1 Christoph Keimel CLA 2011-05-16 06:04:19 EDT 
Created attachment 195709 [details]
testcase project
Comment 2 Christoph Keimel CLA 2011-05-16 06:04:54 EDT 
Created attachment 195710 [details]
Demonstration of the effect (PDF)
Comment 3 Lars Vogel CLA 2019-09-04 03:13:02 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it and remove the stalebug whiteboard tag. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--