> Unfortunately, I think the "robust" way to handle that particular issue is to
> report "sets" of loops - one outer and zero or more inner - as individual
> events, and even using that definition multiple "events" are possible for
> sufficiently complex surface interactions.
Yep, that is exactly what I'm thinking.
> It's more likely that I have - I was thinking each NURBS surface could be
> viewed as a "grid" of Bezier patches, and the intersection logic would
> recognize which "grid patches" on both surfaces had all four edges coincident
> with another surface and which ones had three or less - if those patches are
> delineated by the knots in the NURBS UV space, then you could know which
> "knot patches" were completely involved with a surface/surface event and
> which were only partially involved (hence "outer"). I may not have
> understood your idea fully, or I may be misunderstanding how the Bezier patch
> idea works for the intersection problem.
Maybe I have misunderstood your idea. You originally mean "inner segments",
which may be from the sub-division to Bezier patches. But I also think about
"inner loops", that is, the overlap region may have "holes" in it. How can we
determine the outer loop (and inner loops) after we know the patch is
completely involved or partially involved?
Cheers!
Wu
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
