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

Incompatibility between exchange categories addition in diagram and VP diagram styler #2061

Closed
LisaF268 opened this issue Jan 28, 2021 · 9 comments
Milestone

Comments

@LisaF268
Copy link

When VP diagram styler is active on a diagram, it is not possible to add exchange categories.

Test model 1
Test model 2
No proposed exchange categories with VP diagram styler activated
proposed exchange categories when VP diagram styler is not activated

It is necessary to deactivate the viewpoint to add an exchange category on the diagram.

ebausson-obeo added a commit to ebausson-obeo/capella that referenced this issue Sep 4, 2023
ebausson-obeo added a commit to ebausson-obeo/capella that referenced this issue Sep 4, 2023
ebausson-obeo added a commit to ebausson-obeo/capella that referenced this issue Oct 31, 2023
@SteveMonnier
Copy link
Contributor

Capella2061_exchange_category.zip
Steps to reproduce:

  • Import the Capella project from the attached archive
  • Open the existing LAB diagram
  • Select "FunctionalExchange 1" and go to the properties view
  • The field "Exchange category" should be empty. Select the "..." button
  • On the "Transfer Dialog", double click on "ExchangeCategory1" to move it on the right side. Click on OK.
    -> Validation: Check that "ExchangeCategory1" has been added to the field.

ebausson-obeo added a commit to ebausson-obeo/capella that referenced this issue Nov 16, 2023
When DiagramServices tests an EdgeMapping for selection or visibility,
the disconnect between EdgeMappingImpl and EdgeMappingWrapper is now
managed,
allowing easier integration of external features and plugins into
Capella.
ebausson-obeo added a commit to ebausson-obeo/capella that referenced this issue Nov 16, 2023
ebausson-obeo added a commit to ebausson-obeo/capella that referenced this issue Jan 26, 2024
When DiagramServices tests an EdgeMapping for selection or visibility,
the disconnect between EdgeMappingImpl and EdgeMappingWrapper is now
managed,
allowing easier integration of external features and plugins into
Capella.
ebausson-obeo added a commit to ebausson-obeo/capella that referenced this issue Jan 26, 2024
@pdulth
Copy link
Contributor

pdulth commented Feb 14, 2024

Steps to reproduce:

  • Create a PVMT model applied on Functional Exchange
    image
  • Create an architecture blank diagram displaying an Functional Exchange
  • Display Diagram Styler layer and color the exchange by applying the PVMT property value
  • Create an Exchange Category on the Functional Exchange
  • The Switch Exchange Category display an empty wizard if the Diagram Styler layer is enabled.

@SteveMonnier
Copy link
Contributor

Capella2061_exchange_category_v2.zip
I recreated my sample from Capella master branch and without requiring the VPMS viewpoint that wasn't needed in this context.
@pdulth your changes adding some other calls to DiagramServices.getDiagramServices().isMapping looks good to me, thanks.

@pdulth pdulth added this to the 7.0 milestone Apr 9, 2024
@pdulth pdulth closed this as completed Apr 9, 2024
SteveMonnier pushed a commit to SteveMonnier/capella that referenced this issue Apr 11, 2024
When DiagramServices tests an EdgeMapping for selection or visibility,
the disconnect between EdgeMappingImpl and EdgeMappingWrapper is now
managed,
allowing easier integration of external features and plugins into
Capella.
SteveMonnier pushed a commit to SteveMonnier/capella that referenced this issue Apr 11, 2024
@SteveMonnier
Copy link
Contributor

SteveMonnier commented Apr 11, 2024

Hi @pdulth @tguiu, I noticed that Philippe's commit has been pushed but I missed that Etienne's 2 commits had not been merged as well. I replayed my validation scenario with only your commit and I didn't see the ExchangeCategory in the Transfer dialog so I rebased the 2 commits on the master branch and created this PR: #2848
Thanks.

@pdulth
Copy link
Contributor

pdulth commented Apr 12, 2024

Hi, Can you describe your validation scenario as for me it was ok with the fix.
#2061 (comment)

@SteveMonnier
Copy link
Contributor

Hi,
oh right, I should have added a link as it is "further up" in older messages of this issue: this validation scenario and the scenario migrated for Capella 7.x is in a more recent comment.
Thanks @pdulth.

@roland-huber
Copy link

This problem also exists for Physical Link Categories.

@mPorhel
Copy link
Contributor

mPorhel commented Apr 22, 2024

Issue validated on FunctionalExchange with Version: 7.0.0 Build id: 202404171526 and the following updated sample (with PVMT 70.7.0 and Diagram Styler 70.3.1)

2061_exchange_category_v3_diagramStyler_enabled.zip

ValidationOnVersion-7 0 0-202404171526

The patch proposed by Philippe is generic and deals with Sirius Mapping.
We have just tested with @SteveMonnier a few seconds ago with the addition of a Component Exchange Category in the provided sample + modification of the property scope. And the Switch Component Exchange / Category works fine.
It should be the same for Physical Link Exchange.

@SteveMonnier
Copy link
Contributor

Hi. Indeed, we did some validation this morning and we found at that there had been an issue when I migrated the sample from 6.1 to 7.0. I migrated it again and it works with @pdulth commits. I abandonned the PR I created.

@lredor lredor linked a pull request Jun 5, 2024 that will close this issue
@lredor lredor removed a link to a pull request Jun 5, 2024
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

5 participants