> I was thinking of r56303.
I see. This is about generating a 2D curve on the surface in curve-surface
intersections (the csx_overlap case). The openNURBS doesn't take this into
consideration, though, as it only have m_b[4] in ON_X_EVENT, which can only
represent the start and end of the overlap on surface B. But we sometimes need
a more accurate curve representations. We already get lots of points on the
interior of the curve due to sub-division, so we can use these points to
generate a polyline curve (or fitting into some simplified forms) to better
represent the CSI overlaps.
Unfortunately, the implementation before r56303 might put these points in the
wrong order. So I discard some of them currently, which can reduce the
resolution of the curve (about the half of the original). It's still possible
that we get a curve of the original resolution by using a mapping of m_a and
m_b (m_a should be in an increasing order, so we can decide the order of
m_b's). But this requires extra complexity, and can slow down the performance,
so I haven't done this yet. The current resolution is already enough (usually
hundreds or thousands of points on the curve)
Cheers!
Wu
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
