Community
Participate
Working Groups
The use of fixed sizes for the event and gateway element results in shifted process elements in roundtrip scenarios: If you open a BPMN 2.0 model from a different modeling tool, which uses different sizes, the ancor points of the sequence flows are not in line anymore. If you in turn open a file change with the designer, you will have this problem in the other modeling tool. We implemented the following: * Scale event and gateway sizes up to the dimension defined in the DI bounds * Take the size of the last event/gateway defined in the DI of the current diagram as new default for the creation of that elements. This will align the two modeler sizes during export / import. The bigger picture is: export a model from a web based designer like signavio / oryx / whatever -> enrich the model with implementation details in the designer -> import back to the web designer. See our changes here: https://bitbucket.org/camunda/patches.eclipse.bpmn2-modeler Would be great to see this in master! Best Regards, Andreas
Thanks Andreas! I've merged in the changes from https://bitbucket.org/camunda/patches.eclipse.bpmn2-modeler which was current as of today. If you are planing on maintaining a parallel fork, you should probably take another snapshot from https://git.eclipse.org/c/bpmn2-modeler/org.eclipse.bpmn2-modeler.git because I have made quite a few bug fixes and enhancements since last time.
