#519 BPMNEdge not rendered correctly when it has only 2 waypoints

[Anonymous]

When an edge has only 2 waypoints, it is not rendered correctly. It appears that in this case, the editor uses a default point on the source and target element, instead of the specified waypoints.

For example, refer to the files connect2.png and connect3.png. Note that in connect2.png, the edge attaches to the center of the sub process, even though the corresponding edge in the XML specifies otherwise. By inserting a (superfluous) waypoint, it gets rendered correctly, see connect3.png.

For reference, the relevant part from the XML is:

      <bpmndi:BPMNEdge id="Flow_18od839_di" bpmnElement="Flow_18od839">
        <di:waypoint x="188" y="250" />
        <di:waypoint x="270" y="250" />
      </bpmndi:BPMNEdge>

and

      <bpmndi:BPMNEdge id="Flow_18od839_di" bpmnElement="Flow_18od839">
        <di:waypoint x="188" y="250" />
        <di:waypoint x="220" y="250" />
        <di:waypoint x="270" y="250" />
      </bpmndi:BPMNEdge>

Since the edge is a straight, axis-aligned line, the additional waypoint (220, 250) should not be needed.

[史耀强(Blenta)]

This bug is fixed in version 6.1.4.u1.
This update will be automatically downloaded and installed.

[史耀强(Blenta)]

Currently the update system dos not work properly. I will fix this issue in the new release 6.1.5.

[Anonymous]

Thanks again for the quick fix. I tried it with the new 6.1.4.u1 and can confirm it works correctly now.