-
Notifications
You must be signed in to change notification settings - Fork 100
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
Port allocation are deleted when moving component ports from one component to another #2062
Comments
…y of target's ancerstors
…y of target's ancerstors
…y of target's ancerstors
…y of target's ancerstors / Please enter the commit message for your changes. Lines starting / with '/' will be kept; you may remove them yourself if you want to. / An empty message aborts the commit. / / Date: Mon Jul 10 16:28:01 2023 +0200 / / On branch conservation-port-delegation / Your branch is up to date with 'github-perso/conservation-port-delegation'. / / You are currently cherry-picking commit 08a4af4. / / Untracked files: / .project / common/plugins/org.polarsys.capella.common/.settings/org.eclipse.jdt.ui.prefs / core/plugins/.project / core/plugins/.settings/ / core/plugins/org.polarsys.capella.core.sirius.analysis/.settings/org.eclipse.wst.validation.prefs / releng/cdo/features/.project / releng/cdo/features/.settings/ / releng/cdo/plugins/.project / releng/cdo/plugins/.settings/ / releng/plugins/.project / releng/plugins/.settings/ / samples/.project / samples/.settings/ / tests/plugins/.project / tests/plugins/.settings/ /
…y of target's ancerstors
…y of target's ancerstors
…y of target's ancerstors
Capella2062Port_allocation.zip
|
…ts with existing allocations.
Following the last update, there are 2 more scenarios to validate from the same sample and same diagram:
#3 Steps to validate:
|
…unctionExchange Drag and dropping a port of a functional exchange that is allocated to a ComponentExchange will not remove its allocation anymore.
2062test_functional_exchange_allocation_on_move.zip
|
…y of target's ancerstors
…ts with existing allocations.
…unctionExchange Drag and dropping a port of a functional exchange that is allocated to a ComponentExchange will not remove its allocation anymore.
…y of target's ancerstors
…ts with existing allocations.
…unctionExchange Drag and dropping a port of a functional exchange that is allocated to a ComponentExchange will not remove its allocation anymore.
Context : a functional exchange is allocated to a component exchange, and related functions ports to components ports.
When the component port is moved from one component to another, the allocation link between the moved component port and the related function port is lost.
Allocation links between the other function/component ports and functional exchange/component exchanges are ok.
It is necessary to redo the allocation between the function port and the component port or between the functional exchange and component exchange to solve the problem
The text was updated successfully, but these errors were encountered: