Than you "visose". The previous post is explaining in a better way my problem. BTW I am always engaged by your thinking process! (And I need to reflect sometime to digest them). I am collecting them in my treasure chest.
On Jan 22, 3:43 am, visose <[email protected]> wrote: > The slider expression has the same effect as connecting the slider to > an expression component (i think), only more limited since the only > variable available is the current value of the slider. > I think the best solution is what you did at the right, use a > percentage. You can't change the maximum value of the slider to > curve's length each time the curve changes length. If you want the > slider to represent an actual length (meters, etc.) set the highest > value of the slider to the highest value a curve may have. The problem > here is that for most curves you may set a higher value that the > maximum length of the curve. > > You could add an expression afterward that compares the slider value > and the curve length. If the slider value is bigger than the curve > length, then use the curve length as the actual value. > > On Jan 22, 5:51 am, CAD-NY <[email protected]> wrote: > > > Hi David, > > few days ago on the Post "wish: input to sliders' > > you told me about the expression editor inside the Slider and that I > > could use it somehow to insert the Slider itself as a Variable. > > I can't get around this challenge of mine to understand this problem i > > am facing. > > Here is an image of it. > > >http://grasshopper3d.googlegroups.com/web/Slider_VAR_Input.jpg?hl=en&;... > > > The solution on the right is not so practical because the slider will > > never point to the real value I am tying to assign. > > I read the post on Global Variables. That could fit into the Slider > > but I got you points on that. > > > Any workaround for this? > > > marco
