In definitions with long refresh times, why does the simple fact of double-clicking on the value in a slider to change it have to take so long.
I’m not sliding ! Just changing to a new typed-in value.
Shouldn’t the Slider component just freeze and wait until a new value is set before refreshing the definition downstream ?
I can emulate this behavior by disabling the solver, changing the value, and enabling the solver.
Why doesn’t GH do exactly that ?
I’ve noticed this same behavior. And I’ve tried the same things you have to minimize it’s effect. I’ve found the method that seems to work best is to first disable the component to which the slider is connected, then change the slider as desired, and then re-enable what it is connected to.
My guess about why all this happens is that, when you first activate (not a precise GH term) the slider GH recognizes this and says “uh-oh, there’s going to be a change here, so I better make sure everything down-range is working ok.” GH then recalculates everything changing the slider will affect, and only then does it enable the slider for actual change.
Of course I have no idea what is actually causing the delay (and I really don’t want to know), but it would be nice if the GH crew found a way to eliminate it.
That’s not a viable solution, whether it works or not.
I believe you - and pardon this silly question but how zoomed in are you when double-clicking the slider? 
Countless of times this happens to me unless I really zoom in and then double-click a region on the slider that is not the little circle in it. When you’re not zoomed in enough and on top of it you double-click right on the circle any micro movement on your mouse will still ‘slide’ it a tiny bit. I bet this behavior is more or less obvious depending on specific mouse speed/sensitivity configurations.
Oh, I zoom, man… I zoom.
I see - had to ask. You have an issue then. Good luck!
With big definition, if by mistake you slide an “early” slider… it’s fear. Just fear.
Yeah, zoom in and put the value you want. Single shot. A single lone recalculation wave.
No problems here, even with big definitions. Double click is always fast.
Oisure, maybe you have some GH plugins that interact with its UI? Have you tried running grasshopper without external plugins, with the “loadonebyone” command…
Metahopper and POD come to mind.
I tried the “loadonebyone” method… got bored clicking “yes” after the 100th click.
Another annoying fact is that even when you edit the boundaries of the slider, without changing the current value, it seems to recalculate downstream.
It makes no sense.
Also, even WHILE I’m typing the new value, GH is half-frozen.
Hi, I´ve just updated Rhino to Version 8 SR14 (8.14.24345.15001, 2024-12-10) from some “about one year old” version and experience the same problem. It is really annoying. Is this a bug?
