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

UMLPackage sometimes does not let children go #177

Open
SuspiciousActivity opened this issue Jul 1, 2021 · 0 comments
Open

UMLPackage sometimes does not let children go #177

SuspiciousActivity opened this issue Jul 1, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@SuspiciousActivity
Copy link
Contributor

Describe the bug

Children are sometimes not correctly removed from a parent element, the parent element just extends its bounds to include the child. This happens with ActivityDiagrams (if you move anything out of an Activity) and with UseCaseDiagrams (if you move a UseCase out of a System), but does not happen in a ClassDiagram (with a Package node) and in a DeploymentDiagram (with a Node).

To Reproduce

  1. Open up Apollon
  2. Create a new ActivityDiagram
  3. Move an Activity node in there and make it big
  4. Move an Action node into the Activity node
  5. Move the Action node outside of the Activity node
  6. The Activity node extends its bounds instead of letting the Action node go outside
  7. Same goes for moving a UseCase node out of a System in a UseCaseDiagram

Expected behavior

The Action node should be able to move outside of the Activity node.

Screenshots

Before moving the Action outside:
Screenshot_1
After trying to move it outside:
Screenshot_2

Environment

 - OS: Windows 10
 - Browser: Chrome, Firefox
 - Version: Chrome 91.0.4472.124, Firefox 89.0.2

Additional context

I did some debugging on my own and it appears to me that when moving the Action outside, the Action in children here should not be there, at least this is the case in both working diagrams. While looking at the call stack, I also saw that in both working diagrams the call originates from here, while in the non-working diagrams, it does not.

@SuspiciousActivity SuspiciousActivity added the bug Something isn't working label Jul 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant