RhinoIntersectBreps

Replies to This Discussion

Permalink Reply by Jon Mirtschin on August 28, 2009 at 3:52pm

The SDK function returns true if it encountered no errors/problems whilst assessing the intersection. I've always counted the number of resulting curves or points to check if the objects intersect. Someone else might have a better way.

Cheers,

Jon

Permalink Reply by Damien Alomar on August 29, 2009 at 9:11am

Yea, you have to watch this...I guess the RhinoScript expectation is that is if something doesn't work than it has "failed". I guess the SDK has more gray areas than that, so its definitely best to check whatever variables that were passed into the functions and see if they've been filled. Note that this isn't he only method that exhibits this behavior, but I can't remember which other common ones do.

Permalink Reply by Morten Bülow on August 31, 2009 at 10:53am

Thanks for the replies…
Still having a problem determine, if there is an intersection or not. Here is the code:

Dim intsec As Boolean
Dim crvs() As IOnCurve
Dim pt As On3dPointArray

intsec = RhUtil.RhinoIntersectBreps(x, y, 0.01, crvs, pt)
If crvs Is DBNull.Value = True Then

Print("No intersection")
Else
Print("Intersection")

End If

A = crvs

Attachments:

• intesection_test_2.ghx, 62 KB

Permalink Reply by Damien Alomar on August 31, 2009 at 9:48pm

Crvs won't be null, instead it will be an empty array. So the best thing to do is to see what the bounds of the array are (or the count or something). I'm not at a computer that I can write a little sample, but I'll try to get a quick example tomorrow.