Originally created object disappears when i rerun the script

I do hope with you that the 2022 version will resolve the issues.

There might be some confusion so to make clear: I am not against binding as a mechanism. Session based binding is great. Geometry that updates while you are finetuning the graph is perfect. I wrote hundreds of nodes in C# and they all are hooked up to the binding mechanism. The issue here is the forced persistancy and especially the binding data saving in the graph. As a user I want the option to lose the connection when I’m done finetuning. And I am not convinced the binding data should belong to the graph, unless the graph is inseparable connected to one drawing.

So, if the develop team decide that the binding belongs to the graph, make it optional at least. I am not alone in this. Just do a search on ‘element binding’, ‘disappear’, and so on. Just reread this topic and you see others struggle with this too. Just a few other topics about this:

1 Like