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
I have read through this issue multiple times: #20
I have implemented a switch case very similar to code found in that issue.
I have three different options of curvature.
No center calculation
Center_X calculation
Center_Y calculation
The problem I am facing is that the optimal route of the curve depends heavily on the input/output port being used.
As I have four ports that are input/output ambiguous (stacked on top of each with x-index changing).
Sometimes the horizontal port connecting to a top port should have no curve as the best line.
Or a port across from another would be best with a center_x approach.
I have attached a very poorly drawn guide trying to demonstrate the issue.
Where the curve line runs along the side of the node.
All of this to say, what do you think the best approach is here?
I have looked into connection start/connection end/node moved events to try to determine the ports in use.
But the createCurvature function only uses (start_x, start_y, end_x, end_y) so there are null reference possibilities by using variables existing outside of the curve function.
It is possible this is an unsolvable request. But just wanted to reach out for any potential advice!
Thanks!
The text was updated successfully, but these errors were encountered:
I have read through this issue multiple times:
#20
I have implemented a switch case very similar to code found in that issue.
I have three different options of curvature.
The problem I am facing is that the optimal route of the curve depends heavily on the input/output port being used.
As I have four ports that are input/output ambiguous (stacked on top of each with x-index changing).
Sometimes the horizontal port connecting to a top port should have no curve as the best line.
Or a port across from another would be best with a center_x approach.
I have attached a very poorly drawn guide trying to demonstrate the issue.
Where the curve line runs along the side of the node.
All of this to say, what do you think the best approach is here?
I have looked into connection start/connection end/node moved events to try to determine the ports in use.
But the createCurvature function only uses (start_x, start_y, end_x, end_y) so there are null reference possibilities by using variables existing outside of the curve function.
It is possible this is an unsolvable request. But just wanted to reach out for any potential advice!
Thanks!
The text was updated successfully, but these errors were encountered: