Ah, I see. The thing about it being a "list" is actually a bit
misleading. All parameters (which is what I call those black hexagon
objects) are capable of storing lists of data, which is why the
description always includes the word "list".

The variable parameter is a utility parameter which performs data
conversion for a number of basic types. For example, Rhino uses a
class called On3dPoint to represent 3d coordinates. On3dPoint is
nothing more than 3 numbers and a bunch of functions to do with point
mathematics. In Grasshopper however, point objects are much more
complicated since they can reference Rhino geometry. Hence, every
point in Grasshopper knows if it's a standalone point, or if it refers
to the start of a certain curve and so on and so forth. Many data
types in Grasshopper are more complicated than you need them to be,
which is why the Variable parameter converts complex types into simple
ones which makes it easier to use them inside a Scripting component.

Incidentally, if you double click the icon on the panel you can see
the help-topic for that component/parameter/object. Help is also
available through the context menu of any object on the canvas.

--
David Rutten
Robert McNeel & Associates





On Nov 14, 5:33 pm, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> no, not the list flag, the variable list object in the script category
> panel.
>
> On Nov 14, 12:11 pm, David Rutten <[EMAIL PROTECTED]> wrote:
>
> > Hi US,
>
> > are you referring to the List option in the input parameters of
> > scripting components?
>
> > If so, then list will change the way the parameter feeds data into the
> > component. Most parameters in Grasshopper are not lists, because the
> > components operate on a single data item at a time. However, sometimes
> > you need lists because multiple inputs have to be combined to create a
> > single output (such as Lofting, where multiple input curves become a
> > single surface; or Polyline, where any number of points are used to
> > create a single curve).
>
> > If you enable the List option on inputs, it will change the signature
> > of the Script function, and it will treat all the data inside that
> > parameter as a single blob (i.e. it will not iterate over the data).
>
> > --
> > David Rutten
> > Robert McNeel & Associates
>
> > On Nov 14, 12:42 pm, "[EMAIL PROTECTED]"
>
> > <[EMAIL PROTECTED]> wrote:
> > > what does this list do beyond holding any streams flowing into it?
> > > does it interact with the scripting components in a special way?
>
> > > jonathon- Hide quoted text -
>
> > - Show quoted text -

Reply via email to