Hi Bas, there is a component that allows you to fairly easily get the midpoint of a curve. You can accomplish all these conversions relatively easily. I was wondering if it was worth it to make it happen ALL the time. I'm not talking about components here, I can add components all you like, I'm talking about what happens when you plug a list of closed polysurfaces into the vertex input of a polyline component. Should Grasshopper complain it makes no sense or should it calculate the Volume centroid of each polysurface and then connect all those points with a polyline?
Incidentally, it wouldn't speed up anything, since the Volume calculation still has to be done. It doesn't matter where it happens, it will take the same amount of time. -- David Rutten [email protected] Robert McNeel & Associates On Jan 24, 2:35 pm, bas <[email protected]> wrote: > Hi David, > > I would appriciate such basic functions. Midpoint of a line or curve > would be a function I will often use. The Volume centre is now > possible via Volume, but this is slowing down the script due to the > volume calculation. I would like to add: length, breadth and hight of > a bounding box. > > Cheers, > Bas > > On Jan 23, 7:33 pm, David Rutten <[email protected]> wrote: > > > Does it make sense to anyone to have default conversions for: > > > Curve -> Point (start point? mid point? end point? centre of > > bounding box?) > > Surface -> Point (centre of bounding box? centre of UV domain?) > > Brep -> Point (bounding box centre? Volume/Area centroid?) > > Mesh -> point (?) > > Box -> Point (... etc. etc.) > > Twisted Box -> Point > > Generic Geometry -> Point > > > And, if so, how would you expect it to work? > > > Thanks, > > David > > > -- > > David Rutten > > [email protected] > > Robert McNeel & Associates
