When I’m writing a compiled C# Grasshopper component - I often run Rhino in the debugger.
If I disable a node in Grasshopper (for whatever reason) and there are C# script nodes downstream of that node then I get a prompt in Developer Studio asking for the source location of the compiled script node code and then some exceptions are caught.
I could disable the exception catching but I’d rather see them in case my own code throws them.
So, if I want to disable a node then I have to, manually, disable any following script nodes, in reverse, back up to the node that I want to disable.
If I want to reenable the node and any following nodes then, again, this is a manual process.
Is there a way to persuade Grasshopper to disable downstream nodes? (Maybe I missed an obvious feature and am the last to know of it).
If not: could you (the Rhino dev types) add this feature?
That way I could turn stuff of and on again without having to, manually, do something that the software could do.
-PS
Even outside of a debugging session…
I have a Grasshopper file that makes a fair number of discrete parts of my model?/world?/thing?
Each part involves a chain of nodes (or sub-trees) and some nodes can take 10-20mins to process.
So I tend to have many node sub-trees disabled if I’m not making changes to the parts that they make.
So now and then I will have to disable the current sub-tree and enable another.
It would be nice if Grasshopper could walk down from a sub-tree’s root and do a temp disable or remove a temp disable for me.