One thing would greatly help the UX of editing Custom Nodes, and it’s something you can see “prototyped” (i.e., implemented) in Grasshopper – when you edit a custom node from a definition, it should pass the input data into that Custom Node while you’re editing it. Without real data flowing through the wires, it is very hard to debug, and it’s non-trivial to create the necessary data types from within the custom node definition. The solution is ugly… copy-pasting the contents into the base definition, connecting up wires, editing, copy-pasting back to the custom node, rewiring inputs + outputs.
Perhaps I’m missing something, is there a better way?
Marc