| Summary: | Reconnect edge tool does not work as described in the documentation at the .odesign level | ||
|---|---|---|---|
| Product: | [Modeling] Sirius | Reporter: | Amine Kechaou <aminekechaou> |
| Component: | Diagram | Assignee: | Jessy Mallet <jessy.mallet> |
| Status: | CLOSED FIXED | QA Contact: | Julien Dupont <julien.dupont> |
| Severity: | normal | ||
| Priority: | P3 | CC: | julien.dupont, maxime.porhel, pierre-charles.david |
| Version: | 4.1.1 | Keywords: | triaged |
| Target Milestone: | 5.1.0 | ||
| Hardware: | PC | ||
| OS: | Windows 10 | ||
| Whiteboard: | siriuscon2016, backport | ||
|
Description
Amine Kechaou
Hi Amine, Note: https://www.eclipse.org/sirius/doc/specifier/diagrams/Diagrams.html#edges documentation describes the behavior of the different edge mappings. The reconnection tools section is below (but there is no direct link, look for "Reconnect Edge" section in the same page) For the Reconnection Tool case, you documentation indicates: > The body of the tool is evaluated on the target semantic element of the edge that the user wants to reconnect, > with the following variables available to describe the reconnection: > . source: the semantic element which is pointed before the reconnect. > . target: the semantic element which is pointed after the reconnect. > . sourceView : the graphical element which is pointed before the reconnect. > . targetView : the graphical element which is pointed after the reconnect. > . otherEnd : the edge end (graphical element) that has not changed during the reconnection > . edgeView : the Edge after the graphical reconnection > . diagram : the current Diagram. > . element: the semantic element of the current edge. There is also an image to illustrate this on the reconnectTarget case. Note that if you are dealing with a reconnect tool for a Relation based Edge, the semantic element of the edge will be the semantic element fo the source node. Note that we recommend to avoid the creation of reconnect "both" tools, as making two distincts tools for reconnect source and reconnect target is generally simpler and easier to maintain. Hi Amine, Thanks for your detailed bug report. It seems that there is effectively an issue around the completion and the validation mechanism on the VSM side. Nevertheless, it's not yet in the scope of a future release. Regards, Maxime org.eclipse.sirius.diagram.business.internal.dialect.description.DiagramToolInterpretedExpressionTargetSwitch might need to have a specific behavior for the caseReconnectEdgeDescription an other entry possible entry point might be org.eclipse.sirius.business.api.dialect.description.AbstractInterpretedExpressionQuery.getAvailableVariables() Sorry to move this, but we won't have the resources to work on this for 5.0. Marking as a backport candidate for a future 5.0.x if possible. Fixed with resolving bug 508556 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=508556) Commit: http://git.eclipse.org/c/sirius/org.eclipse.sirius.git/commit/?id=7d83ced3b2347d2e888e3a4898e15aab66cd7d3f Available in Sirius 5.1.0, see https://wiki.eclipse.org/Sirius/5.1.0. |