Force recompute of value listner

[parametricmonkey1 (Paul Wintour)]

Hi @andheum

If I understand correctly the base configuration is to have a default slider (which shouldn’t be updated) and then a value listener component to hear the values from the dashboard.

Setting the listener to ‘live’ makes sense. But if you disable ‘live update’ how can you force the component to recompute without modifying the default slider? It seems to contradict the logic.

Do you need to use F5 recompute or is there another way I should be doing it. I’m guessing from this post, there a Metahopper component which does this?

Essentially I want the user to update lots of sliders and have a ‘data dam’ before those updated values trigger anything downstream.

Thanks

[dharman]

Pretty sure you can add another T trigger input to the listener with the ZUI.

[andheum (Andrew Heumann)]

@dharman is correct. This just came up in another topic:

Human UI: Single button for all the inputs

There’s a pattern for these situations that I like. The value listener on your text inputs is set to “manual input” (disable “Live” in the right-click menu) and triggered with a “live” value listener on an update button (Should probably be a “true only button” so it only fires once per click). It’s easier shown than described: [trigger-button] commit-button.gh (10.0 KB)

[parametricmonkey1 (Paul Wintour)]

@andheum @dharman thanks that worked