Bug 154520 - [CommonNavigator] Wizard ordering not controllable in popup
Summary: [CommonNavigator] Wizard ordering not controllable in popup
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows 2000
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Francis Upton IV CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-21 07:59 EDT by Fred Rotbart CLA
Modified: 2019-09-06 16:08 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fred Rotbart CLA 2006-08-21 07:59:09 EDT
When a number of "new" Wizards with the same menuGroupId are contributed to the CommonNavigator they are always presented in the popup menu in alphabetical order rather than in the order that they were specified in the org.eclipse.ui.navigator.navigatorContent extension.

A use case, for example, would be to maintain consistancy Wizard ordering in the File/New main menu with their ordering in the Common Project Explorer popup.
Comment 1 Michael D. Elder CLA 2006-08-21 11:39:09 EDT
There is a groupId attribute associated with the commonWizard element that will allow you to group related wizards together. While this isn't the same order as the perspective wizards under File > New, it can provide organization for related wizards.
Comment 2 Fred Rotbart CLA 2006-08-21 11:56:32 EDT
(In reply to comment #1)
> There is a groupId attribute associated with the commonWizard element that will
> allow you to group related wizards together. While this isn't the same order as
> the perspective wizards under File > New, it can provide organization for
> related wizards.
> 

Yes I am using this feature, but, as you noted, this does not affect the ordering within the grouping.

When each of the new wizards represents an element in a hierarchial ordering such as New Project, Class, Field, etc., the loss of consistant ordering becomes very obvious.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:08:34 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.