Allow defining custom behaviour for floating edges

[MeMeMax]

Hi,

in my usecase we need floating edges, but instead of having the edges bundled in one place and going from there to another node we would need orthogonal edges which go directly to the other node. As far as I can see this is not yet possible even with custom routing since we can't control the destination point of the route, right?

Here is a schema on how it should look like - the small nodes are sources and the large one is the target:

[lukasz-jazwa]

You’re correct, with floating edges user currently can’t control the exact connection point on the node. Floating edges are meant for simpler scenarios where users just want nodes connected without worrying about precise attachment points, and where defining ports would be unnecessary overhead.

We do plan to make floating edges more configurable in the future, but that work hasn’t been prioritized yet, so I can’t provide a timeline.

For your use case, the recommended approach would be to use ports and compute their positions dynamically on your side based on the relative positions of the nodes. That gives you full control over where the orthogonal edges connect.

At the moment we’re focused on fixes and smaller improvements needed to ship the next release as soon as possible. Once that’s out, we’ll come back to this thread and share an example of how you can achieve this using dynamically positioned ports