|Type Selection Dialog Issues [message #954118]
||Mon, 22 October 2012 16:05
| Michael Swiercz
Registered: October 2012
I truly appreciate the convenience of the Recent selections list in Papyrus's Type selection dialog, letting me quickly select previously used types when adding Operation parameters. Unfortunately, this only seems to work with types defined within the current model and does not apply to imported package elements (e.g. Java Primitives, other models, etc.)|
Steps to repeat problem with Java Primitive Types
1. Add an operation to a class or interface.
2. Click Add Elements from Owned parameters.
3. Give parameter a name and edit the reference type by clicking ... for Type.
4. Traverse the model to the boolean Java primitive (e.g. model-> <Package Import> Java Primitive Types -> importedPackage(1) -> <<ModelLibrary>> JavaPrimitiveTypes->boolean)
5. Click OK and OK once more.
6. Click Add Elements again.
7. Assign another element name and edit its reference type.
8. boolean will be listed in Recent selections. Issue: Upon selecting boolean in the list the OK button remains disabled. The only recourse is to re-traverse the model tree to its definition.
Interestingly, when adding properties setting their type as "bool" and using CTRL-SHIFT finds its primitive declaration without a hitch. Edit: I have a sneaking suspicion that Recent Sections only retains the main model component's name rather than the full path to the component.
Feature Suggestion for Type selection dialog
1) It would be a time saver if the dialog remembered what model tree nodes were expanded rather than having to repeatedly drill down into multi-level packages.
2) When specifying a Filter value, the model tree immediately displays matching entries similar to Eclipse's Preference filter.
[Updated on: Wed, 24 October 2012 02:27]
Report message to a moderator
|Re: Type Selection Dialog Issues [message #985666 is a reply to message #985252]
||Thu, 15 November 2012 11:12
| Camille Letavernier
Registered: February 2011
Edit: I have a sneaking suspicion that Recent Sections only retains the main model component's name rather than the full path to the component.
No ; that's actually a bug in the search/reveal algorithm. The history retains the full URI to the selected element. However, the search algorithm is not able to browse the "import package" links, and cannot retrieve the imported libraries.
It should be fixed in Juno SR2.
Powered by FUDForum
. Page generated in 0.02477 seconds