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 want to create connections, that go in the opposite direction as the default (from right to left). Basically it should represent a backward connection, e.g., going from a node back to it's previous node.
I already managed to create custom nodes with special sockets for these backward connections (and adapt their position), however, the styling is still a little bit off, as the connections normally go from the left to the right, so they start off at the right side of an input socket and enter the output socket from their left side.
Is there a way to configure connections or sockets to adapt the path of a connection to directly go to the left without these "swerves"?
I'm using Angular 17 and therefore the rete-angular-plugin, as well as the connection-path-plugin.
Cheers
(also sorry, if this is the wrong request, my company only allows bug and maintenance requests...)
Suggested Solution
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Description
Hi there,
I want to create connections, that go in the opposite direction as the default (from right to left). Basically it should represent a backward connection, e.g., going from a node back to it's previous node.
I already managed to create custom nodes with special sockets for these backward connections (and adapt their position), however, the styling is still a little bit off, as the connections normally go from the left to the right, so they start off at the right side of an input socket and enter the output socket from their left side.
Is there a way to configure connections or sockets to adapt the path of a connection to directly go to the left without these "swerves"?
I'm using Angular 17 and therefore the rete-angular-plugin, as well as the connection-path-plugin.
Cheers
(also sorry, if this is the wrong request, my company only allows bug and maintenance requests...)
Suggested Solution
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: