| Summary: | [Sequence Diagram] General Ordering support | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Vincent Hémery <vincent.hemery> |
| Component: | Core | Assignee: | Vincent Hémery <vincent.hemery> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 0.7.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Vincent Hémery
On a same lifeline, in fact, the norm specifies that the Y location always gives the correct sequencing. So placing a General Ordering between Occurrence specifications of a same Lifeline will either : - be useless, (redundant with the location on the lifeline) - be erratic (conflicting with Y location). In such a case, an error message will be shown to the user. For the moment, this action will not be forbidden. General ordering is almost completely handled. This includes moving all elements attached to an occurrence specificaiton when this one is moved. This includes handliong of stereotypes as an external label. Only the drag and drop is not yet handled. D & d is now correctly handled. In addition, naming of created elements has also been handled. Finally, this feature has been disable between Occurrence specifications of a same Lifeline. |