Modifying a disabled component in the group causes the Stream Filter to recompute.
This really isn’t necessary. There’s not even any data coming out of the disabled components. This is problematic in heavy definitions.
Here’s a simple example:
stream-filter_problem.gh (23.1 KB)
@wim who’s responsible for this?
Hi Martin -
I’ve file that as RH-87876 Grasshopper: Disabled Input Causes Stream Filter to Recompute
By default, Andy Payne is set to be the assignee for Grasshopper 1 issues these days.
From your .gh file:
This Data Dam is on but does not trigger. This tells me the problem is within the Stream Filter.
But is that actually the case? Doesn’t any downstream component from a disabled component get recomputed?
-wim
My video shows two data dams and I clicked both arrows to send data through. Then I plug in the cable again from the initial XY plane to the disabled plane component. See how the first data dam triggers but not the second one?
Anyway, what is the benefit of recomputing when a disabled input is triggered? No benefit for me…
