Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Imported edges do not support overriding behavior #554

Open
darets97 opened this issue Feb 11, 2025 · 2 comments
Open

Imported edges do not support overriding behavior #554

darets97 opened this issue Feb 11, 2025 · 2 comments

Comments

@darets97
Copy link

Context

We are working on a customer specific extension to the UML2 activity diagram from UML Designer that relies heavily on Guards defined on ControlFlowEdge. For this reason we have created a layer, inside of which we define an Edge Import that we use to modify the Center Label to display the edge's guard rather than it's name. Unlike Node Imports, we are unable to change the Behavior (found in the Behavior tab in the Sirius Specification Editor), and as a result we cannot change the Double Click Description to display a custom window including a guard, or the Label Direct Edit to directly edit the guard.

Expected behavior

When clicking on an imported edge in the Sirius Specification Editor, the Properties tab should allow the Behavior to be changed for Edge Import similar to Container Import .

Image
The Properties tab for Edge Import without the Behavior tab present

Image
The Properties tab for Container Import with the Behavior tab present

Solution
Add a Properties tab for Edge Import in the Sirius Specification Editor

@dhendriks
Copy link

This would be great to have resolved!

@GlennPlou
Copy link
Contributor

Indeed, EdgeMappingImports can only be used to define conditional styles. The behavior could be improved, but this kind of development is not part of our roadmap. As this feature is rarely used, there's hardly any chance of this enhancement being developed by our team without funding.

Otherwise, I suggest you find another solution, even if it means duplicating some mappings. There's a good chance this will be as efficient, even if it's not very aesthetic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants