Dynamic input of min/max range of sliders?

[jdelrocco (Joe Del Rocco)]

Is there a way to send inputs into sliders (or equivalent component) so their range is dependent upon a previous computation? I have some sliders with ranges that should be set dynamically based upon upstream computations. The downstream slider ranges don’t make sense after certain upstream calculations.

I saw the ‘expression’ part of the slider, but I’m not sure how to use that yet.

Also, I know Python, in case you have a solution that is easily scriptable?

This looks like a similar question:

Domain Slider

Hey! Some time ago i found a picture in the internet of a slider where you can input a domain and then slide between these min an max values. but im not sure if this component really exists because i do not find it in grasshopper. has anyone an idea where i can find this “slider” or does this component not exist? [sliders]

[Amir_Habibi (Sag)]

I haven’t found such thing though ( tell me as u found it ) in grasshopper , But you could use range component simply and input the range .

[piac (Giulio Piacentino)]

Have a look if this helps:

The only safe way to Update Sliders in GhPython

Over the years, there have been lots of threads here and on the old Grasshopper forum that deal with setting slider values in Grasshopper. They all have some advantages and disadvantages, but they have something in common: they too often end up breaking the Grasshopper SDK rule “never edit values while the definition is running”. This thread shows a way of fixing that. This is a Rhino-6-only possibility, because this feature is new in Rhino 6. By overriding the Component Context menu, we can se…

[Marco_Traverso]

Wouldn’t be enough to use a RemapNumbers components?

You could have a slider with a 0 to 1 range and then use the values from the computation to set the range of a second domain used to remap the slider’s value. Basically the slider would act like a percentage of the interval between two dynamic numbers. Or am I missing something?

[jdelrocco (Joe Del Rocco)]

Thank you very much! All of these are fine solutions for me.

Technically, I don’t have to update the ranges/domains of the downstream sliders at all. I just thought it would be more accurate to do that, since the ranges/domains are dependant upon upstream inputs. This would be a problem if for example someone new to my project were to start using the downstream sliders, not knowing that the ranges/domains were not accurate due to changes they made in upstream sliders/inputs. So I wanted to reset the ranges/domains of the downstream sliders only after the upstream inputs were changed, that’s all. It makes the file more accurate in my opinion.

Also, @Marco_Traverso , the relationship is not linear, but your suggested solution I’m sure could easily be updated with respect to a function.

[qythium]

There is also a component in Metahopper for doing that, I posted some examples of it in the other thread:

Problem Controlling Range of Sliders with Python

Hi, I been having some difficulties trying to change the range of multiple sliders using GhPython, as the range get reduce the ticks of the slider jumps out of the bar, I believe it has to do with the way I’m managing the solution, I was wondering if someone could take a look at the script and tell what I’m doing wrong. Thanks!!! Control Sliders Python.gh (11.3 KB)

[jdelrocco (Joe Del Rocco)]

Thank you

[tom.frode.hansen (Tom F. Hansen)]

Hi, yes I have also used the component “Set slider properties” in Metahopper, that solves this problem with 2 components only, i.e the get and set components. You can then set the domain of the slider dynamically.