Community
Participate
Working Groups
Created attachment 184955 [details] Screenshot depicting the problem in question. I20101209-0255 Now I only get one project menu item and a separator.
The double update(boolean) calls to MenuManager seems to be the problem here. Changing update(false) to update(true) did not help.
It seems to be the same general problem as the one uncovered in SwitchToWindowMenu. Since the contribution item is not deemed to be dirty, we don't think there is a need to "regenerate" the items and the existing ones gets disposed.
This is enough to kill the submenu. It seems to me like the 'a.b.c' bit should be respected? Shouldn't I be targeting a view there anyway? <extension point="org.eclipse.ui.menus"> <menuContribution locationURI="popup:a.b.c?after=group.new"> <menu id="new" label="New"> <command commandId="org.eclipse.ui.window.nextView" style="push"> </command> </menu> </menuContribution> </extension>
What extension in Mylyn is causing this?
(In reply to comment #4) > What extension in Mylyn is causing this? The 'org.eclipse.mylyn.commons.team' bundle's plugin.xml contributes this snippet of XML. I don't have any reason at the moment to believe that this is a problem on Mylyn's end though.
(In reply to comment #3) > This is enough to kill the submenu. It seems to me like the 'a.b.c' bit should > be respected? Shouldn't I be targeting a view there anyway? > > <extension point="org.eclipse.ui.menus"> > <menuContribution locationURI="popup:a.b.c?after=group.new"> > <menu > id="new" > label="New"> > <command > commandId="org.eclipse.ui.window.nextView" > style="push"> > </command> > </menu> > </menuContribution> > </extension> The 3.x behaviour is to merge all of the menus at a given level with the same ID. So if there's already a "new" menu we should be applying our MMC to that existing one. PW
Cannot reproduce with I20110620-1631 on Windows XP. I'm quite positive this was fixed by the changes for bug 340565. *** This bug has been marked as a duplicate of bug 340565 ***