| Summary: | Selection box of "Defining Feature" should be restricted to valid features | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Andreas Graf <graf> |
| Component: | Views | Assignee: | Project Inbox <mdt-papyrus-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | charles, graf, johan, klaas.gadeyne, kristof.berx, papyrus-bugs, peter.cigehn |
| Version: | 0.10.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Andreas Graf
Build id: I20130204-1400 In order to overcome this problem you can directly drag an drop a classifier (from the model explorer) on an instance specification (on the diagram). As a result a popup will show up allowing you to select the different properties for which you need to create slots. Regards *** Bug 333734 has been marked as a duplicate of this bug. *** (In reply to Camille Letavernier from comment #1) > Build id: I20130204-1400 > > In order to overcome this problem you can directly drag an drop a classifier > (from the model explorer) on an instance specification (on the diagram). As > a result a popup will show up allowing you to select the different > properties for which you need to create slots. Now this is one *nifty undocumented* feature that could have saved me a couple of hours... [*] Nevertheless, the original bug still stands for version 1.1.3 IMO, * this bug should also block Bug 358077 ([Property View - UML] The UML property view should be improved for usability concerns) * Bug 367652 is definitely (also/yet another?) a duplicate of this bug [*] (being greedy now) It would be even better if this would work recursively, ie. if a new instance specification would be created for slots whose defining feature itself is a classifier :-) |