You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .changeset/orthogonal-edge-routing.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,4 +2,4 @@
2
2
"@tumaet/apollon": minor
3
3
---
4
4
5
-
Edges now route themselves far more cleanly. They avoid unnecessary corners and crossings, run straight when two shapes line up, leave a node from a suitable side, and divide each available node side into balanced grid-aligned stretches — one edge centres itself, two edges make three even gaps, and larger groups spread the same way — instead of piling into a corner, stepping when they could be straight, or looping around another edge. Required-interface sockets stay concentric with their interface circles, including interfaces imported at an older size; relationship lines stop with visible breathing room before the socket, while its arc adapts to the sides the finished routes actually use. Pin multiple endpoints to the same seat to form a stable shared junction; its common trunk is preserved intentionally, and opposing pinned branches use a balanced grid-aligned turn lane. Dragging an endpoint preserves its attachment while the route remains eligible for layout; dragging a bend preserves the route you authored. In both cases, neighbouring edges adapt without jumping on release, and node dragging remains substantially more responsive in edge-dense diagrams. Automatic results are deterministic, so every collaborator and a reloaded page see the same picture. Existing v3 diagrams and older v4 files with pre-routing edge data continue to open and are upgraded automatically.
5
+
Edges now route themselves far more cleanly. They avoid unnecessary corners and crossings, run straight when two shapes line up, leave a node from a suitable side, and divide each available node side into balanced grid-aligned stretches — one edge centres itself, two edges make three even gaps, and larger groups spread the same way — instead of piling into a corner, stepping when they could be straight, or looping around another edge. Required-interface sockets stay concentric with their interface circles, including interfaces imported at an older size; relationship lines join the socket cleanly, while its arc adapts to the sides the finished routes actually use and remains visually distinct from neighbouring sockets and provided edges. Pin multiple endpoints to the same seat to form a stable shared junction; its common trunk is preserved intentionally, and opposing pinned branches use a balanced grid-aligned turn lane. Dragging an endpoint preserves its attachment while the route remains eligible for layout; dragging a bend preserves the route you authored. In both cases, neighbouring edges adapt without jumping on release, and node dragging remains substantially more responsive in edge-dense diagrams. Automatic results are deterministic, so every collaborator and a reloaded page see the same picture. Existing v3 diagrams and older v4 files with pre-routing edge data continue to open and are upgraded automatically.
0 commit comments