<div dir="ltr">
<div>At<br></div><div><a href="https://www.vtk.org/doc/nightly/html/classvtkDecimatePolylineFilter.html#details" target="_blank">https://www.vtk.org/doc/nightly/html/classvtkDecimatePolylineFilter.html#details</a><br></div><div><br></div><div>States<br></div><div>
<dl class="gmail-m_-7191597960660642828gmail-section gmail-m_-7191597960660642828gmail-warning"><dt>Warning</dt><dd>This algorithm is a very
simple implementation that overlooks some potential complexities. For
example, if a vertex is multiply connected, meaning that it is used by
multiple distinct polylines, then the extra topological constraints are
ignored. This can produce less than optimal results.</dd></dl><div><br></div><div>Is above warning code for "crash at following lines"<br></div><div><br></div><div> void Remove(vtkIdType vertexIdx)<br> {<br> this->Size--;<br> (*(this->Vertices[vertexIdx].prev)).next = this->Vertices[vertexIdx].next;<br> (*(this->Vertices[vertexIdx].next)).prev = this->Vertices[vertexIdx].prev;<br> }</div><div><br></div><div>in vtkDecimatePolylineFilter.cxx class vtkDecimatePolylineFilter::Polyline<br></div><div><br></div><div>?</div><div><br></div><div>I
have multiple distinct polylines housed in vtkPolyData. I can seem to
do batch mode operations, *not that this documented anywhere mind you*,
with vtkParametricFunctionSource for splines and
vtkSmoothPolyDataFilter for smoothing.... decimation errr not so much.<br></div><div><br></div><div>The
goal which seems to work for some vtk classes (
vtkParametricFunctionSource
and
vtkSmoothPolyDataFilter
) but not for others (vtkDecimatePolylineFilter) is to house a network
of lines connected in a graph, but not a simple graph node to node,
which do not represent some geometry say like a circle or polygon, but
rather a network of paths and nodes. Goal was to put in pipeline with
optional decimation, smoothing or spline, but then goes the crash at
decimation.</div><div><br></div><div>Just what are those "potential
complexities" and the bit about overlooking say like bad memory access.
next has a pointer, but prev pointer not so much (NULL). Hey what
about overlooking error checking and null pointers. Clearly it seems to
be overlooking that.</div><div><br></div><div>apologies for repost of "(no subject)" this one has a titile.<br></div><div><div class="gmail-adL"><br></div></div></div>
</div>