Hi David, thanks for answering. I'm not proposing a new loft component, what I'm proposing it's a new component that collect and make a list with the input geometry through the input numer slider (an integer range). The surface component (or curve component) will calculate just one solution for the set of curves, points, etc. that is determinated by the number slider value. I upload an image: http://groups.google.com/group/grasshopper3d/web/Loft%20and%20NSlider%20-%20slider%20collect%20component%20request.PNG?hl=en I hope that help to explain myself....
I was hoping that the new version have some kind of solution to these problem, but i'm not seeing it... Well I have another wish-request. Can you make that the number slider can be modified in one step by pressing the right or left key on the keyboard? I want to make a macros in a external program that change the number slider and bake de loft component (a rough solution to the same problem...) Thanks for everything, Manuel. David Rutten wrote: > Hi Manuel, > > Thank you for posting the files. I see what you mean. I have a number > of ideas on how to solve this problem, I think I can make it work > without the need for additional components such as sliders. > The way grasshopper networks work make your suggestion pretty > complicated. There's no way at present for a component such as Loft to > calculate a series of solutions and collect all the results. It's also > weird because Loft is supposed to collect all the resulting surfaces, > while all the other components that are part of the logic are supposed > to only carry the last set of data. > > -- > David Rutten > Robert McNeel & Associates > > > > > On Oct 6, 8:23�pm, "Manuel A." <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I upload an example (Loft and NSlider.wrm, Loft and NSlider.3dm). > > In that example i make a loft between two curves and the first number > > slider its controlling the set of curves for the loft component. > > I want a component that take all the geometry that produce the loft > > component through the "animation" of that number slider. Like I said > > before, you'll use the same number slider to set the points, curves, > > etc. to modified the resulting loft, curve, etc. > > > > In that way it's solved the problem that some component only produce > > one output like loft, sweep1, curve, polyline, etc. and I think that > > it'll be very easy to implement because its just a new component, its > > not necessary two dimensional arrays or change those components to > > accept other kind of data or input. > > > > Thanks again, > > > > David Rutten wrote: > > > Hi Manuel, > > > > > I don't get it. Which problem is this supposed to solve? > > > > > As far as the official wish-list goes, sure, post it here. I'll make > > > sure it ends up on the McNeel bug/wish tracker. > > > > > you can animate a slider through the slider menu, but I have a feeling > > > we're not talking about the same kind of "animation" here. > > > > > -- > > > David Rutten > > > Robert McNeel & Associates > > > > > On Oct 5, 1:20 am, "Manuel A." <[EMAIL PROTECTED]> wrote: > > > > Hi! > > > > Is these the official wish list? > > > > > > well.. i have an idea for a "loop component". > > > > The input A will be a component with a single object, not a list (a > > > > resulting loft surface, sweep1, single curve, etc). The input B will > > > > be a Number Slider component. > > > > > > The idea is that de Loop Componente will animate the slider trought > > > > all the numbers, getting all the different objects of the A input > > > > making a list with these objects (so you could get a list of loft > > > > surfaces, curves, etc). > > > > > > Obviously you'll use the same number slider to modified the resulting > > > > loft, curve, etc. > > > > > > Maybe there is a way to animate a number slider that I'm not aware? > > > > > > Thanks for your work, > > > > > > Manuel.
