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

Bug 320316

Summary: the "original" editor stack is special
Product: [Eclipse Project] e4 Reporter: Oleg Besedin <ob1.eclipse>
Component: UIAssignee: Project Inbox <e4.ui-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: Lars.Vogel, remy.suen
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Bug Depends on:    
Bug Blocks: 321864    
Attachments:
Description Flags
Screenshot none

Description Oleg Besedin CLA 2010-07-19 15:52:15 EDT
Created attachment 174668 [details]
Screenshot

- on a clean workspace create a project with a file or two 
- open an editor
- drag open editor say, under the Package Explorer.

See the screenshot attached.

Problems:
- The original editor stack is now empty
- The original editor stack is shared with, say, debug perspective, but it is empty; the editor(s) are in a different stack
- The original editor stack has "maximize" botton, but the new editor stack has "minimize" button (and does not maximize on double-clicks)

It looks like the "original" editor stack is special and is different from editor stacks created by, say, drag-and-drop.

This fits well into 3.x's "editor area", but I was hoping to see more flexible behavior in e4.

(This is on I20100718-2237.)
Comment 1 Eric Moffatt CLA 2010-09-21 13:36:14 EDT
See bug 322432. This is the expected behavior but it's not the stack that's special, it's the editor 'area' itself (since it's the area that gets shared between perspectives...)

We also have a related issue of how to handle views that are dragged inside the editor area because they can't be in two places at once (i.e. if the view 'V' would 'normally' have been in a view stack in perspective 'A' what happens if we drag 'V' into the editor area in some other perspective and then switch to 'A'?)

See bug 321864 for more details.
Comment 2 Lars Vogel CLA 2015-02-04 06:27:23 EST
AFACS this bug is outdated.