-
Notifications
You must be signed in to change notification settings - Fork 320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node inputs still keep a reference to removed nodes. #419
Comments
Your description is exactly right, and creating a new node named 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. In a future update, I'd like to add support for calling |
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). That's interesting that |
Yes, I believe it's just an oversight that 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. |
Hey there, this is more of a question.
But in the following example:
The output will be:
As you can see, there is still a reference to "node1", which as a node, no longer exists.
I'm not sure if this is a bug or not, but if It's not, is the intention suppose to be that you can now create a new "node1" which will neatly fit in its place?
The text was updated successfully, but these errors were encountered: