Community
Participate
Working Groups
Please provide a generator option or other means by which create child/sibling menu items can be organized into submenus (based on feature name) if so desired. Currently, for models with many types and containment features, users must often scroll to menu to find the desired item. Also, it can be confusing if the name of the feature is the same as the type of the child/sibling (e.g. imagine a containment feature named 'foo' and a type named 'Foo' - will result in 'Create Child > Foo Foo').
Created attachment 61432 [details] proposed changes
Created attachment 61439 [details] oops forgot these changes
Created attachment 61645 [details] Reviewed patch I've reviewed the patch. It mostly looked good, but I've made a few changes: 1. I updated it to patch against the changes from bug 178708. 2. I updated the Rose model. 3. I fixed a few picky things like hyphenating "sub-menu" in UI and comments, and adding space after commas. 4. I fixed the one error I found, a missing cast in the new depopulateManager() method when not using generics. 5. Since you felt compelled to fix the ID typo in the existing populateManager() Javadoc, I felt compelled to regen to pickup that change in all our editors. So, now it looks all good to me. Any changes you'd like to discuss?
Kenn's enhancement is committed to CVS.
The changes are available in build I200703221305.
Move to verified as per bug 206558.