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

Bug 468771

Summary: [EditorMgmt] AreaRenderer creates single CTabFolder for two editors
Product: [Eclipse Project] Platform Reporter: Markus Kuppe <bugs.eclipse.org>
Component: UIAssignee: Platform-UI-Inbox <Platform-UI-Inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: daniel_megert
Version: 4.5Keywords: triaged
Target Milestone: ---   
Hardware: PC   
OS: All   
Whiteboard: stalebug
Attachments:
Description Flags
Screenshot none

Description Markus Kuppe CLA 2015-05-29 06:13:46 EDT
Created attachment 253924 [details]
Screenshot

1. Open two editors (by default they are stacked)
2. Drag one of the editors to the right or left-hand side of the other
3. A single CTabFolder is created as the bar above *both* editors with only a pair of min/max buttons. The rest of the bar is screen cheese.

Aside from the visual glitch, it's questionable if the editors should be grouped at all. Moving the second editor anywhere else makes sure it becomes a first class UI citizen with its own pair of min/max button.

The bug can be observed on Linux, Win and Mac with 4.4 and 4.5. The bug is somewhere located in org.eclipse.e4.ui.workbench.renderers.swt.AreaRenderer.synchCTFState(MArea).
Comment 1 Eclipse Genie CLA 2019-05-26 16:44:51 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 2 Eclipse Genie CLA 2021-05-19 01:02:41 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. 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.