Hello everyone,
I’ve been noticing for a while that disabling a hops input still shows up when you call it as a Hops function (img.2), or in a webapp (img.3&4), unless you delete it.
I believe this wouldn’t be the desired effect from this. For us, it can go beyond a nice-to-have, we imagine scenarios where certain inputs’ display could be blocked (disabled) if certain criteria are met, with the whole logic being handled on the GH side.
Any thoughts about this?
first_text_disable.gh (5.2 KB)
Many thanks,
Abdo.