Node inputs still keep a reference to removed nodes. about materialx HOT 3 CLOSED

Yes, I believe it's just an oversight that add2.setConnectedNode('in1', None) doesn't break the connection, and we'll fix this in an upcoming change. My sense is that this call should actually remove the input element from the node, rather than leaving the input with an empty nodename string.

We don't yet have a high-level method that removes all invalid connections from the document, but this sounds like a good suggestion for a future improvement.

from materialx.

Your description is exactly right, and creating a new node named node1 will neatly replace the original, restoring the connection between node1 and node2.

From a high level, the philosophy of the MaterialX API is that all document edits are local, so modifying or deleting an element in one place (e.g. node1) doesn't edit any other elements in the document. If you'd like to remove the input element from node2, you can delete it in the usual way by calling add2.removeInput('in1').

In a future update, I'd like to add support for calling add2.setConnectedNode('in1', None), which would perform the same work and make a clearer parallel with add2.setConnectedNode('in1', add1).

from materialx.

Oh I see, thank you for taking the time to explain this, the layering paradigm makes perfect sense.

Is there any general way to remove "ghost" references of this kind (or would that basically be, iterating every node, checking if it has a connection string but no connected node and pruning it at such).
I can imagine some sticky problems arising from a unexpected reference popping back into play, due to a lapse in remembering to break connections.

That's interesting that add2.setConnectedNode('in1', None) doesn't do the equivalent of add2.removeInput('in1') as add2.getInput('in1').setConnectedNode(None) does prune the reference.
Would the intention be that add2.setConnectedNode('in1', None) edits the underlying noderef?

from materialx.