Andrew, I'll have a look at the Area calculation. The entire Grasshopper solution is encapsulated in a Try...Catch block, meaning that any crashes which still happen point to a bug deep down in Rhino code.
Thanks for sending it in, David -- David Rutten Robert McNeel & Associates On Nov 16, 5:40 pm, Andrew <[EMAIL PROTECTED]> wrote: > I have a grasshopper file that populates a surface with triangular > panels of varying sizes. Each triangular panel is generated by two > fixed points and a variable point, and when the variable point is at > the same place as one of the fixed points, its area is zero, but > grasshopper still generates a line-like surface. If I measure the area > of such a surface in Rhino, it comes out to be some infinitesimally > small number. I want to cull out all surfaces under a certain area > threshold, but any time one of these near-zero-area surfaces is fed > into the area component, the program crashes. > > Wanted to bring the problem to your attention and ask if anyone had > any suggestions for a workaround. Hope my description was clear enough > -- I can post an example file if necessary. > > Thanks! > > Andrew
