Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339717 - No min/max support *within* the shared area
Summary: No min/max support *within* the shared area
Status: RESOLVED WORKSFORME
Alias: None
Product: e4
Classification: Eclipse Project
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Eric Moffatt CLA
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-11 11:31 EST by Eric Moffatt CLA
Modified: 2019-06-05 07:28 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Moffatt CLA 2011-03-11 11:31:49 EST
We currently have the same issue as 3.x...once you split the shared area there is no way to manage its layout.

Should each area have its own trim?
Should we support sash adornments like '<' and '>' ?

We might consider expanding the scope of this defect to include the more general discussion about workflow scenarios that arise from our enhanced presentation capabilities...
Comment 1 Jonas Helming CLA 2014-04-09 15:31:03 EDT
We want to be able to maximize the children of an Area, if they are opened next to each other, individually. So a maximize of a child would look like a maximize of a part in a partstack, with all children in the area being minimized as well as all other elements in the workbench.

We would prepare a contirbution for this. If this should not the default behavior, we could make it depending on a tag. What do you think?
Comment 2 Eclipse Genie CLA 2018-10-18 15:25:16 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. 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.

--
The automated Eclipse Genie.
Comment 3 Lars Vogel CLA 2019-06-05 07:28:15 EDT
This is a mass change to close all e4 bugs marked with "stalebug" whiteboard.

If this bug is still valid, please reopen and remove the "stalebug" keyword.