I have a fairly complicated gh script that queries Revit with maybe 15 different nodes. Each time I place anything, even just a panel for example, gh recomputes for 5-20 seconds and is basically frozen/flashing. From what I can see online, this is a known Revit issue and it can probably be controlled by adding data dams to “Query” type nodes.
While thinking about this I wanted to propose to devs an idea I had.
- Rhino.Inside could ship with a special boolean toggle called “r-i-toggle” or whatever.
- For each “expensive” Rhino.Inside node, there could be a simple function added to its code that acts kind of like a data dam to prevent the auto-recomputes. This function would check the r-i-toggle state and either dam the data for those nodes that have the function injected, or if True, let all data freely flow.