RouteGraph is able to render itself properly but picking the routeline to split at shows unexpected results
This is related to the examination and fixing of #549 (closed).
shows problems in Apros associated with splitting of route graph connections under certain conditions.
These conditions seem to currently require:
- splitting at a persistent route line where the "previous" routeline is transient
- the other end of the route graph to be connected to a diagram flag already (at least a diagram-local flag)
In the example image above, it seems to me that the RoutePoint
information accessible through e.g. the rightmost vertical RouteLine
being split, contains coordinates that do not reflect the actual corner coordinates in the rendered connection line. I'm not even sure if it is supposed to be this way, but this at least makes RouteLine.collectSegments
return wrong data. In this example case the Segment
returned for the rightmost vertical line is actually something like (79,0) - (79,70)
when I would expect it to be (79,70) - (79,92)
or similar.
Anyway, this will need @niemisto for debugging. I can't hack it.