Bugzilla – Full Text Bug Listing
| Summary: | [Perspectives] [Wizards] New... > Items order not consistent | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Shaun Skelton <shaun> |
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 | CC: | Karice_McIntyre, remy.suen |
| Version: | 3.2 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux-GTK | ||
| Whiteboard: | stalebug | ||
|
Description
Shaun Skelton
I can't reproduce this on Win2K. Can you provide more specific steps? Shaun showed me the case using the Plug-in Development perspective. The item for the Product Configuration wizard was first, but after a no-op customize perspective, it got moved down to the middle. Reassigning bugs in component areas that are changing ownership. Is this still a problem in 3.3? PW yes - in 3.3 M2. Check the order of items in the Java perspective, then go to Custumize perspective, change nothing and hit OK. The items are now in a different order. Paul, I can reproduce this on I20080715-1015. 1. Use -data to point to a non-existent folder. 2. Eclipse starts up with the 'Java' perspective. 3. File > New... > Java Project, New Project... / Package, Class, Interface, Enum, Annotation, Source Folder, Java Working Set, Folder, File, Untitled Text File, JUnit Test Case / Other... 4. Right-click on the toolbar, select 'Customize Perspective...'. 5. Click 'OK' to close the dialog. 6. File > New... > Java Project, New Project... / Package, Class, Interface, Source Folder, Enum, Annotation, Java Working Set, JUnit Test Case, Untitled Text File, Folder, File / Other... 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. 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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie. |