Community
Participate
Working Groups
Here is a piece of code from WorkbenchPage: if (part instanceof MultiEditor) { part = ((MultiEditor) part).getActiveEditor(); } // Activate part. //if (window.getActivePage() == this) { IWorkbenchPartReference ref = getReference(part); internalBringToTop(ref); setActivePart(part); see? when an EditorPart is an instance fo MultiEditor, then all part active operation will effect on the active editor in this MultiEditor. Why not let MultiPageEditorPart have the same treatment? They are the editor that can combine other editors, they need the same feature. I'm tired make the active editor in MultiPageEditorPart have it's own PropertyPage and OutlinePage.It's an nightmare.
We are looking at a more "component" like view of both editors and views. One of the things I'd like to see it do is to make MultiPageEditorPart work as more of a "first class citizen" and to remove hacks like the one for MultiEditor that are in the code. PW
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.
