Bug 54265 - [EditorMgmt] CTabFolder.single=true should position chevron differently
Summary: [EditorMgmt] CTabFolder.single=true should position chevron differently
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Duong Nguyen CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-10 06:53 EST by Kai-Uwe Maetzel CLA
Modified: 2019-09-06 16:12 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kai-Uwe Maetzel CLA 2004-03-10 06:53:18 EST
I20040309
The multiple editor tab preference is diabled. In this build the editor tab is 
no longer presented as a tab which makes it look a bit nicer.

Major issue:
Switching editors is only possible by clicking on the >> button which is now 
even more difficult to spot as there is no tab border.
-> The >> button should always be at the same position.
Comment 1 Michael Van Meekeren CLA 2004-07-06 14:16:17 EDT
I think it is more important that the close X not move around.  
Comment 2 Douglas Pollock CLA 2004-07-08 15:51:27 EDT
The positioning of the buttons in the single mode is off.  It is not normal for 
the "x" button to appear on the left in any application I've seen.  It is 
typically on the right (at least for us left-to-right language people).  Plus, 
I agree with Kai that the changing positions is a bit frustrating. 
 
It might be better to position the buttons and text as follows: 
left-aligned: <chevron> <title> .... right-aligned: <zoom> <close> 
 
This more closely mimicks the standard window manager decorations for KDE, 
GNOME and Windows XP. 
Comment 3 Veronika Irvine CLA 2004-07-13 11:06:28 EDT
But not the Mac : )
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:12:48 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.