| Summary: | [ActivityDiagram] support "standalone pin" notation | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Raphael Faudou <raphael.faudou> |
| Component: | Diagram | Assignee: | Arthur Daussy <arthur.daussy> |
| Status: | REOPENED --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | arnaud.cuccuru, cletavernier, faure.tristan, juan.cadavid, klaas.gadeyne, raphael.faudou |
| Version: | 0.8.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Raphael Faudou
Please reopen with a description if this is still an issue Not a bug, but rather an enhancement. This is alternate notation for pin and makes diagrams easier to read and to edit. Changed status (re open) and importance (enhancement) Hi, The title is not really explicit. Please provide a description and/or reference to the description in the specification in UML 2.5 it is described in fig 16: The situation in which the OutputPin of one Action is connected to the InputPin of the same name in another Action via an ObjectFlow may be shown by the optional notations of Figure 16.6. The standalone Pin in the notation maps to an OutputPin and an InputPin and one ObjectFlow edge between them in the underlying model. This form should be avoided if the Pins are not of 464 the same type. Multiple arrows coming out of a standalone Pin rectangle is an optional notation for multiple edges coming out of an OutputPin. (See other ObjectFlow and Pin notations in sub clause 15.2. The specific notational variant used shall be preserved when the diagram is interchanged, see Annex B.) Figure 16.6 Standalone Pin notations *** Bug 468989 has been marked as a duplicate of this bug. *** |