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
Currently creating three edges between a pair of nodes will create this clutter:
This is of course not very useful, and I therefor propose fromOffset and toOffset. The properties store an integer for the pixel offset of the edge. Where 0 is center of the side, positive being 'up' the side and negative being 'down' it. Meaning a positive offset will push the edge towards the positive axis of the side. For example, with toSide: 'bottom' will toOffset: -100 push the edge arrow 100 pixels towards -x (left).
Offsets other than 0 need to be clamped with in sideLength/2 and -sideLength/2, as the edge shouldn't be able to start and end past the node side.
The properties are optional and default to 0 (the center) when not defined.
fromOffset
andtoOffset
propertyCurrently creating three edges between a pair of nodes will create this clutter:
This is of course not very useful, and I therefor propose
fromOffset
andtoOffset
. The properties store aninteger
for the pixel offset of the edge. Where0
is center of the side, positive being 'up' the side and negative being 'down' it. Meaning a positive offset will push the edge towards the positive axis of the side. For example, withtoSide: 'bottom'
willtoOffset: -100
push the edge arrow 100 pixels towards -x (left).Offsets other than
0
need to be clamped with insideLength/2
and-sideLength/2
, as the edge shouldn't be able to start and end past the node side.The properties are
optional
and default to0
(the center) when not defined.fromOffset
(optional, integer) is the pixel offset on the side where this edge starts.toOffset
(optional, integer) is the pixel offset on the side where this edge ends.This proposal shouldn't be considered done. I will try to accommodate any feedback.
The text was updated successfully, but these errors were encountered: