Bug 71805

Summary:	[EditorMgmt] tabs: Remove editor drop-down menu and keep compressing
Product:	[Eclipse Project] Platform	Reporter:	Rob Jones <rob.jones>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	3.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Rob Jones

2004-08-11 12:37:52 EDT

Hi

Just upgraded to 3.0.0 from one of the MX 3.0 builds.
I notice a change in behaviour if I have lots of editor windows (10+ but varies
with screen width and view positions) 

Pre 3.0.0: As many tabs as I had open editors would appear in the tab bar with
less and less space being used per tab as more editors were openened.

3.0.0: Once a limit if reached a '>>' symbol appears on the right with a number
representing how many "untabbable" editors there are. The ">>" opens a drop down
box that lets me choose my editor.

Personally I prefered the pre 3.0.0 method. I deal with a lot of files typically
and I find the ">>" drop down list more time consuming and unintuitive to deal with.

Could we have one of 

A) A choice of either method configurable in the preferences.

B) To stop the -ve side of the pre 3.0.0 method (being that the tabs got very
small and you couldnt read names) could we have an option so that instead of the
">>" symbol an additional row(s) of tabs were used.

Sorry for the lengthy explanation. Hope it makes sense. If not please ask.

thanks

Rob

Comment 1 Rob Jones

2004-08-11 12:38:48 EDT

sorry I forgot to say please.
"please"

Comment 2 Douglas Pollock

2004-09-28 12:30:23 EDT

I'm trying to gather all the tab related bugs....

Comment 3 Michael Van Meekeren

2006-04-21 13:19:39 EDT

Moving Dougs bugs

Comment 4 Susan McCourt

2009-07-09 19:06:03 EDT

As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009

Comment 5 Boris Bokowski

2009-11-17 13:02:27 EST

Remy is now responsible for watching the [EditorMgmt] component area.

Comment 6 Eclipse Webmaster

2019-09-06 16:10:55 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.