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

Sequence flows to message events are not attached to center #887

Closed
stephanpelikan opened this Issue Aug 22, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@stephanpelikan

stephanpelikan commented Aug 22, 2018

If you use pools and visualize message flows by dragging dotting arrows to message events then those arrows are not attached to the center of that message event (see video: Sequence flows to message events are not attached to center.zip). You have to emend it manually. Sometimes it is only a little amount, so only orderly persons may see the effect, but sometimes it is easy to see for everyone. In some circumstances it is snapped exactly to the center but those situations are rare - generally it is not.

I use version 1.16.2

@nikku

This comment has been minimized.

Show comment
Hide comment
@nikku

nikku Aug 22, 2018

Member

Thanks for reporting this issue.

The behavior itself is intentional, as users should be able to specify the exact docking position of the message flow on the target element. This is required for docking on tasks as seen in the screen cast below.

foo

One could argue that this "feature" makes no sense when connecting from / to events, as the resulting diagram is almost always ugly. I suppose consistent snapping to the elements center (cf. snapping on sequence flow creation; second part of screen cast) would improve things?

Member

nikku commented Aug 22, 2018

Thanks for reporting this issue.

The behavior itself is intentional, as users should be able to specify the exact docking position of the message flow on the target element. This is required for docking on tasks as seen in the screen cast below.

foo

One could argue that this "feature" makes no sense when connecting from / to events, as the resulting diagram is almost always ugly. I suppose consistent snapping to the elements center (cf. snapping on sequence flow creation; second part of screen cast) would improve things?

@nikku nikku referenced this issue Aug 22, 2018

Closed

Snap message flows to target center during connect #850

0 of 2 tasks complete
@nikku

This comment has been minimized.

Show comment
Hide comment
@nikku

nikku Aug 22, 2018

Member

Adding consistent snapping for message flows on creation is tracked via bpmn-io/bpmn-js#850.

Member

nikku commented Aug 22, 2018

Adding consistent snapping for message flows on creation is tracked via bpmn-io/bpmn-js#850.

@nikku nikku added this to the M24 milestone Aug 22, 2018

nikku added a commit that referenced this issue Aug 22, 2018

@nikku nikku closed this in 1f588d3 Aug 22, 2018

@wafflebot wafflebot bot removed the backlog label Aug 22, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment