generative modeling for Rhino
Can anyone tell me how, or if it is possible fundamentally to have:
2 sliders that are inserted into a function, and as one slider is changed the other slider is affected, for example as the fist slider is increased, the second decreases according to the function?
ok so this is an older post about slider wishes :) take a look at my proposition
all slider's functionality stays like it's now, only making it easier and faster to change domain
... and of course take a look at idea of making components lock at canvas, seems quite useful (at least easier to operate on huge amount of components on canvas)
...aaand please think about changing all of the selected components links with one click, so there wouldn't be a problem of making all the links hidden fast.
I have been thinking about this recently, particularly when dealing with list item indexes. Remapping can be a pretty ugly solution when you go from having 2 items to choose from and 2000. I usually have a slider with a range of 0-100 and remap from there, but if you have 1000 things you will miss 9 out of 10 items as you slide from 0-100. You could then say well why not have the slider start at 0-1000? Well you could, but then when there are 2 items instead of 1000 it feels silly to have to slide to several hundred numbers to get to the item you want. Or you could change the 100 number slider to a floating point slider, getting you back your extra 9 out of 10 items, but then you are even more diconnected from actual item index you have chosen. You could set up a panel to show you the remapped number and all that but it seems like it could be a lot simpler.
I think if the slider could detect if its connected to a list item and then detect the number of items in the list and then automatically change the upper limit of the slider to match... then that would be great :)
This could either be a new component (item picker?) or an adjustment to the current one. Perhaps in the edit menu of the slider there could be a "list item slider" checkbox.
It seems that just as easily there could be a "when changed..." option category that would contain two boxes: "retain value" and "retain percentage" that users could select depending on what they need (so the problems david mentioned are their problems :) ).
I'm not sure if this is too specific of a case to be desired by enough people, but I would be a very happy camper.
I am just thinking, it might be used so the area or the volume of an object to be fixed and the sliders that control the size of that object to be adjusted.