Bug 111958 - [WorkbenchParts] Option to "semi-maximize" editors tab group to editors area
Summary: [WorkbenchParts] Option to "semi-maximize" editors tab group to editors area
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1.1   Edit
Hardware: All All
: P5 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-10-07 13:46 EDT by Ian Graham CLA
Modified: 2019-09-06 16:14 EDT (History)
2 users (show)

See Also:

Attachments
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 Ian Graham CLA 2005-10-07 13:46:20 EDT 
I typically do Java development using the Java Browsing perspective with two 
side-by-side tab-groups in the editors area.  However, when I switch to other 
perspectives, the editor area changes aspect ratio so as to make my editors 
annoyingly narrow.  Also, I get the same issues when I do a comparison.

Right now my only option is to maximize the tab-group I'm working on, but more 
often I'd prefer to "semi-maximize", enlarging the tab-group only to the size of 
the editor area rather than to the whole window.  I'd love to have this 
option(maybe by holding the shift key when I double-click the tab to maximize?), 
and even have the option to make it the default behaviour when I maximize 
editors.
Comment 1 Paul Webster CLA 2006-09-28 11:01:18 EDT 
There are currently no plans to work on this feature.

PW
Comment 2 Denis Roy CLA 2007-06-22 09:33:06 EDT 
Changes requested on bug 193523
Comment 3 Christopher Barber CLA 2008-06-18 09:42:14 EDT 
Also see bug 236716
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:14:20 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.