Hi Andy, many data types in Grasshopper have translation logic build in. If something wants a BRep and you give it a surface, the surface will be converted into a BRep on the fly. The same is true for Numbers and Integers, Colours and Vectors, Arcs and Circles. There are even some fairly exotic translations defined, for example:
Curve -> Number (gives the length of the curve) Curve -> Interval (gives the domain of the curve) Surface -> Interval2D (gives the uv domain of the surface) String -> Number (will evaluate the string, even if it's a complete expression) Interval2D -> Number (gives the area of the interval) There are more auto-conversions, and whenever I add more data types the list grows. -- David Rutten Robert McNeel & Associates On Nov 13, 2:19 am, Rchitekt <[EMAIL PROTECTED]> wrote: > Hi David, > This explanation of the extrude component might explain why I was > having trouble with the Trim component for my waffle system for a poly- > surface. I was using an extruded surface as my Brep for the Trim > command. It seems like the Trim component was specifically looking > for a Brep, but it will not work with the extrude component as the > input for the required Brep for the Trim component (although it > doesn't turn red when connecting the extrude component, as it would if > I just connected a single surface). Anyway, it seems like this is why > it might not be working. Thanks for the explanation. I'm not sure if > there is a work around yet, given my solution, but I'll keep working > on it. > Thanks, > Andy > > On Nov 12, 3:20 am, David Rutten <[EMAIL PROTECTED]> wrote: > > > Hi Carter, > > > The output of the extrude component is a Surface, not a BRep, so I > > cannot return more than one surface per extrusion. When you extrude in > > Rhino, the resulting surface is split along the kinks. I should > > probably do something similar as well since having kinky surfaces is a > > recipe for disaster. > > > I don't know what's wrong with the second example. I'll need to see a > > screenshot of your network (or the network itself). > > > -- > > David Rutten > > Robert McNeel & Associates > > > On Nov 12, 2:25 am, carter <[EMAIL PROTECTED]> wrote: > > > > ok, so i am not an expert with grasshopper, nor do i know much about > > > scripting, but i am trying to build a little grasshopper file and > > > after working for a couple of days on the simplest thing, i need to > > > ask you guys a couple of questions. > > > > first, i set up a file to locate a box on a point, distribute the > > > boxes along some set parameters. simple. right. ok. so first off, i > > > used a rectangle which let me input my point, x, and y values. it gave > > > me a nice little rectangle that is the right dimension. then i > > > extruded it, and then made four copies along a vector. great. but, > > > next i tried to take off a face on each of the boxes. but whilst > > > exploding the boxes to then use a cull on, the boxes only explode into > > > three faces. what the? why doesn't it explode into 6? when hiding > > > everything but the arrayed boxes, the boxes have six faces. could > > > someone explain why the explode thinks it only has 3? and even if that > > > is what i am left with with a logical explanation, how would one > > > remove the same two, opposing faces from each box? > > > > so, while messing around with this, i thought i would change the > > > sequence a little and make boxes right away, instead of rectangles > > > that are then extruded, boxes seem to explode into 6 faces. which is > > > good. but then while inputting the exact same parameters for x, and y, > > > it gave me a box that has no correlation to the x and y values that > > > are being inputted. > > > > i will post an image if need be, but being as simple as this, i don't > > > think i really need to. > > > > thanks a million anybody. > > > > c
