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

Bug 363297

Summary: [CommonNavigator] There is no way to contol the order of wizard groups in the New context menu
Product: [Eclipse Project] Platform Reporter: Sezgin Halibov <Sezgin.Halibov>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: remy.suen
Version: 3.7   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: stalebug

Description Sezgin Halibov CLA 2011-11-09 07:44:52 EST 
Build Identifier: 20110615-0604

As described in https://bugs.eclipse.org/bugs/show_bug.cgi?id=105312, the sorting is based on the alphabetical order of the menu item names. This is applicable also for the groups as they are sorted in the alphabetical order based on menuGroupId attribute of common wizard extention (see org.eclipse.ui.navigator.WizardActionGroup.findGroups()).
When the clients have to give a specific order of the groups in the New context menu, i.e. to place the project wizards at the top, the only way to do that is to play with this attribute. But they do not have control over the order of the wizards that do not have menuGroupId as they automatically are assigned to "all-uncategorized" group.
So to have a complete control over the order of the group separators and wizards shortcuts, the clients should create a custom WizardActionGroup and use it to provide new actions when their extension is active.

A possible solution could be being able to give a custom comparator(or separate comparators for the groups and shortcuts) to be used to sort the groups and shortcuts.


Reproducible: Always
Comment 1 Lars Vogel CLA 2019-11-14 03:49:04 EST 
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.