Small bug when casting an invalid box to geometry base

Hi David, I've encountered a small bug in the casting logic of the script components:

When a geometrybase param is supplied with an invalid box, there's an (escalation kind?) of popup exception, that prevents you from validating the data itself. A bit nicer behaviour could perhaps be to pass it as a null value to the script component.

It's a very minor issue, but still, it can be reproduced (see attached).

Attachments:

bug-cast-invalidbox-geometry-base.gh, 3 KB

Replies to This Discussion

Permalink Reply by David Rutten on November 6, 2014 at 3:15am

Would it be better to have a null, or to cast the Box to a Brep?

Permalink Reply by Arend on November 7, 2014 at 5:37pm

Hmm, not quite sure at this point, what could be a consideration for one or the other to be better?

My test here shows that casting it to a brep (at least calling the ToBrep) also returns null. If it's null it's catchable, and seems a good solution to me.

RSS