-
-
Notifications
You must be signed in to change notification settings - Fork 216
Associate Action with right Partition #3224
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
Conversation
So we only have to override one.
I think this is a nice example of what happens if you do not build your software with TDD. It actually needs a style sheet to work!
# Conflicts: # gaphor/diagram/tests/test_instanteditors.py # gaphor/diagram/tools/tests/conftest.py
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @amolenaar, these changes look good. I gave it a spin and for me the first drop is still being associated with the first swimlane even if I drop it on the 2nd. When I select the action and release it, then it is associated with the 2nd one.
Ah, I only fixed it for moving actions from one partition to the other. Did you drop from the model browser? There no grouping is implemented. Did you drag from the toolbox? I added a TODO for placement tool. Not sure yet how to do the grouping without duplicating the logic. |
In both cases, items should be placed on the right region/partition.
Hi @amolenaar, I was dropping from the toolbox since I thought that would be the primary use case. |
So we can use it to drop any element onto any other element.
Also add some pre-conditions and deal with placing an item outside of a container.
I extended the use of You can now create actions directly on a swim lane, and it's placed in the right swimlane. Somehow this doesn't work that well for state machines. I have not been able to figure out why, yet. |
not via gaphor.modules imports.
So that nested states can still be properly placed afte an `update_shape()` call.
I updated the The problem was that updates caused the shape to be recreated. As a result regions could not be determined. |
@amolenaar Oh nice one! I haven't had a chance to look at the updates yet, but I should be able to make some time tomorrow to do one last review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really nice update to the drop zones @amolenaar!
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Actions are always assigned to the first partition when dragging.
Issue Number: fixes #3050
What is the new behavior?
The partition below the mouse cursor is now found.
Other information