Bug 151488

Summary:	[MPE] MultiPageEditorActionBarContributor.setActivePage is called before setActiveEditor
Product:	[Eclipse Project] Platform	Reporter:	Amy Wu <for.work.things>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	NEW ---	QA Contact:
Severity:	minor
Priority:	P3	CC:	dennis.nguyen.06, panagiotis.korros
Version:	3.2
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Amy Wu

2006-07-21 18:20:33 EDT

Currently, when a multipage editor is first created, its multipageactionbarcontributor's setActivePage is called before setActiveEditor.  This is because in MultiPageEditorPart.createPartControl, setActivePage is called which eventually calls the action bar contributor's setActivePage.  The action bar contributor's setActiveEditor is not called till a little later.

I need setActiveEditor called before setActivePage because I need the multipage editor at some point in setActivePage.

Comment 1 Paul Webster

2006-09-28 15:18:09 EDT

Is this still a problem in 3.3?

PW

Comment 2 Amy Wu

2007-05-02 19:16:54 EDT

Yes, this is still a problem in 3.3.  For more info, you can check out bug #141013 comment #9

Since this is still a problem, I'm going to reopen the bug, but I'll lower the severity to minor since I do have a workaround in place.

Comment 3 Dennis Nguyen

2009-04-08 19:19:19 EDT

*** Bug 270571 has been marked as a duplicate of this bug. ***

Comment 4 Paul Webster

2009-04-09 07:46:03 EDT

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

Comment 5 Eclipse Webmaster

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