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

Improve auto-layouting for circular Boundary -> Activity flows (loop) #467

Closed
pfolthof opened this issue Feb 3, 2016 · 1 comment
Closed
Assignees
Labels
bpmn support Tracks missing BPMN support enhancement New feature or request interaction modeling pr welcome We rely on a community contribution to improve this.
Milestone

Comments

@pfolthof
Copy link

pfolthof commented Feb 3, 2016

Could you please try to draw this arrow (from the boundary event to the owning activity)?

bpmn-io-boundary-example

It would be great if this would be much easier.

@nikku nikku changed the title Arrow from boundary event to owning activity Improved auto-layouting for circular Boundary -> Activity flows Feb 11, 2016
@nikku nikku changed the title Improved auto-layouting for circular Boundary -> Activity flows Improve auto-layouting for circular Boundary -> Activity flows Feb 11, 2016
@nikku
Copy link
Member

nikku commented Feb 11, 2016

We'd need to improve auto layouting for that special case in order to do this.

Good catch.

@nikku nikku added modeling interaction enhancement New feature or request labels Feb 11, 2016
@nikku nikku changed the title Improve auto-layouting for circular Boundary -> Activity flows Improve auto-layouting for circular Boundary -> Activity flows (loop) Mar 2, 2016
@nikku nikku added this to the Backlog milestone Mar 2, 2016
@nikku nikku removed this from the Backlog milestone Feb 14, 2018
@nikku nikku added pr welcome We rely on a community contribution to improve this. backlog Queued in backlog labels Feb 19, 2018
@nikku nikku added the bpmn support Tracks missing BPMN support label Apr 19, 2018
@philippfromme philippfromme added in progress Currently worked on and removed backlog Queued in backlog labels Jul 3, 2018
@philippfromme philippfromme self-assigned this Jul 3, 2018
philippfromme added a commit to bpmn-io/diagram-js that referenced this issue Jul 9, 2018
philippfromme added a commit to bpmn-io/diagram-js that referenced this issue Jul 9, 2018
philippfromme added a commit that referenced this issue Jul 9, 2018
philippfromme added a commit that referenced this issue Jul 10, 2018
philippfromme added a commit to bpmn-io/diagram-js that referenced this issue Jul 10, 2018
philippfromme added a commit to bpmn-io/diagram-js that referenced this issue Jul 11, 2018
philippfromme added a commit to bpmn-io/diagram-js that referenced this issue Jul 11, 2018
@ghost ghost removed the in progress Currently worked on label Jul 11, 2018
nikku pushed a commit to bpmn-io/diagram-js that referenced this issue Jul 12, 2018
nikku pushed a commit to bpmn-io/diagram-js that referenced this issue Jul 12, 2018
Give users more control over the layouted connection by allowing
explicit sites <[t]op, [l]eft, [b]ottom, [r]ight> to be specified
on a connection.

If a side is explicitly given, the layouter will layout a u-turn
if necessary.

Related to bpmn-io/bpmn-js#467
nikku pushed a commit to bpmn-io/diagram-js that referenced this issue Jul 12, 2018
Give users more control over the layouted connection by allowing
explicit sites <[t]op, [l]eft, [b]ottom, [r]ight> to be specified
with the preferred layout.

If explicit outgoing/incoming directions are given, the layouter
will layout a u-turn to enforce the preference.

Related to bpmn-io/bpmn-js#467
nikku pushed a commit that referenced this issue Jul 12, 2018
@nikku nikku reopened this Jul 13, 2018
@nikku nikku closed this as completed in 220c0a7 Jul 13, 2018
@nikku nikku added this to the B26 milestone Jul 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bpmn support Tracks missing BPMN support enhancement New feature or request interaction modeling pr welcome We rely on a community contribution to improve this.
Development

No branches or pull requests

3 participants