Currently, custom sockets are no longer supported for automatic linking
when dropping a node on a link. This is because SOCK_CUSTOM is given a
negative priority and is ignored. To fix this, SOCK_CUSTOM is now given
the lowest priority and the rest of the sockets got their priority
incremented.
Details
Details
- Reviewers
Jacques Lucke (JacquesLucke) Hans Goudey (HooglyBoogly) - Maniphest Tasks
- T93430: Custom node sockets don't get relinked when dropping a node on an existing link
T93438: Custom nodes no longer get inserted in between two linked nodes - Commits
- rB61fe0d626441: Fix T93438: Auto linking do not work for custom sockets
rBab2a7aa0da81: Fix T93438: Auto linking do not work for custom sockets
Diff Detail
Diff Detail
- Repository
- rB Blender
Event Timeline
Comment Actions
I wounder if we can just use the top internal link for the node to make the connection. I could look into that after this is fixed.
Comment Actions
I wounder if we can just use the top internal link for the node to make the connection.
That seems reasonable. Not sure if there are corner cases where this is not the desired behavior.