Hi Bas, I think David was after something slightly different. I'm pretty sure he was asking about specific translation conversions. Meaning, if a component wants a Brep for the input and you give it a surface, the surface will be converted into a Brep on the fly. The same is true for a Curve and a Number. If the component you are working with wants a Number input, and you happen to give it a curve, it will automatically translate that and output the Curve length as a number. There are lots of autoconversions going on, and I think he's asking whether or not we have a preference for some of the new conversion structures. And you should be able to get the length, breadth, and height of a bounding box through using the Box Components (Surface/Analysis/Box Components). Best, Andy
On Jan 24, 5:35 am, 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
