Hi cab, the problem with adjusting slider domains on the fly is that it might force your slider value to be pushed around very aggressively. If you always want your slider to operate on the first 1/3 of the curve length, why not post-process your slider value (which is always between 0.0 and 1.0, or 0.0 and 100.0 or whatever makes sense) to map onto the curve length? Adding more inputs to the slider will make it at least twice as thick, which is also something of which I'm very weary.
That being said, it sounds like it's a great job for a 'leech' object that attaches itself to a slider, and sets the domain whenever necessary... -- David Rutten Robert McNeel & Associates On Oct 1, 3:32 am, cab <[EMAIL PROTECTED]> wrote: > David - > > Kudos on Grasshopper - it really is fantastic. I am posting this here > under the 'wish list.' New functionality of sliders is great, but how > about inputs for 'lower limit' and 'upper limit?' Example: say I want > to use curve evaluation at any point along the first third of a > curve. I could get the length of the curve, divide it by 3, and then > plug that into the 'upper limit' input on the slider. > > Regards - > > cab > > On Sep 30, 2:53 am, David Rutten <[EMAIL PROTECTED]> wrote: > > > Distractions? :) > > > It sounds like having 'leech objects' that attach themselves to > > regular components/parameters and somehow alter the properties might > > be quite an interesting approach. It might even be a solution for > > visual Conditionals and Loops. Now you've got me thinking....... > > > -- > > David Rutten > > Robert McNeel & Associates > > > On Sep 30, 12:01 am, taz <[EMAIL PROTECTED]> wrote: > > > > David, > > > > No, I wouldn't say I'd find it necessary. > > > > When I put together the pdf I thought (in the case of an exploding a > > > box) some may want the individual components results to display > > > differently as direct output. That could still easily be done with > > > an 'attach' color component just like for meshes. > > > > Don't let me distract you with too much talk of colors since I know > > > that's farther down the list. > > > > taz > > > > On Sep 29, 11:37 am, David Rutten <[EMAIL PROTECTED]> wrote: > > > > > Taz, Visose, > > > > > that indeed sounds like an easy fix. I'mnottoo fond of this > > > > particular solution since it might involve some data duplication (the > > > > display code still tends to duplicate data in order to prevent null > > > > points during viewport redraws, but this is something I'm looking > > > > into). > > > > > Taz,doyou really need this kind of control on a per-parameter basis? > > > > Would it be enough to be able to 'attach' some sort of properties > > > > override object to an entire component? > > > > > -- > > > > David Rutten > > > > Robert McNeel & Associates > > > > > On Sep 28, 1:14 am, visose <[EMAIL PROTECTED]> wrote: > > > > > > What taz explains about the layers parameter and component is exactly > > > > > what i visualized that didn't seem to require a big change in how > > > > > grasshopper works, just another component. Add rhino layers as another > > > > > type of object to be able to link from the rhino model just as curves, > > > > > points, etc. The next best thing would be to link materials, and be > > > > > able to change some of it's basic properties through grasshopper. I've > > > > > read that the main users of grasshopper are architects. Architecture > > > > > isnotonly geometry, but also texture, light and color. Make that > > > > > parametric too, please ;)- Hide quoted text - > > > > > - Show quoted text -- Hide quoted text - > > > > - Show quoted text -
