Parallel lines intersected!

Replies to This Discussion

Permalink Reply by Dmitrii Karpovich on June 24, 2014 at 2:10am

version is 

Version 0.9.0075 

Permalink Reply by David Rutten on June 24, 2014 at 8:19am

Yeah that's definitely a bug. I fixed it now, lines that are (anti)parallel to within 0.01 degrees are no longer solved.

--

David Rutten

david@mcneel.com

Permalink Reply by Richard Schaffranek on June 24, 2014 at 8:34am

Could you please link that to drawing precision?

Permalink Reply by David Rutten on June 24, 2014 at 10:11am

Are you sure? The Rhino angle tolerance is often 1 degree, which would be ridiculously large for this purpose.

--

David Rutten

david@mcneel.com

Permalink Reply by Richard Schaffranek on June 24, 2014 at 10:22am

Or e.g. angleTolerance / 1000

It would be just good to have it not fixed to a value...

Permalink Reply by Richard Schaffranek on June 24, 2014 at 10:49am

I mean I wouldn't mind the intersections returns infinity -> concept?

Permalink Reply by David Rutten on June 25, 2014 at 3:25am

How would you use that infinity? How does infinity differ from null in terms of information content?

I can put in an additional input for custom tolerance settings, but I don't do that anywhere else so it would be a little bit weird.

--

David Rutten

david@mcneel.com

Permalink Reply by Richard Schaffranek on June 25, 2014 at 3:36am

So how do you handle floating point imprecision in other components, I always thought you would tap into the drawing tolerance?

Why Infinity:

If you consider 3d space than two parallel lines could return infinity while two skew lines could simply return null -> so you would get a little more information out of it