Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 82472

Summary: [ViewMgmt] [RCP] Forcing a view to be always maximized
Product: [Eclipse Project] Platform Reporter: Pascal Rapicault <pascal>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P5 Keywords: helpwanted
Version: 3.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows 2000   
Whiteboard: stalebug

Description Pascal Rapicault CLA 2005-01-10 09:50:13 EST
For RCP usecase, it is interesting to be able to force a view to be always
maximized.
Comment 1 Nick Edgar CLA 2005-01-10 15:50:32 EST
What was the use case again?  What does it mean to be always maximized?  E.g. if
I create a perspective with views A, B and C, and A is marked to be always
maximized, B and C will never be visible (assuming they're in different folders).

Also, maximizing a view affects all other views in the same folder (and there's
currently no API for folders, other than for defining the initial layout).
Comment 2 Nick Edgar CLA 2006-03-15 11:24:24 EST
Reassigning bugs in component areas that are changing ownership.
Comment 3 Boris Bokowski CLA 2009-11-11 17:30:40 EST
Remy is now responsible for watching the [ViewMgmt] category.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:10:29 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.
Comment 5 Eclipse Genie CLA 2022-01-02 16:55:03 EST
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.