So I've added this in an .cpp file and complied it:
vtkStandardNewMacro(MyD3)
MyD3::MyD3()
: vtkDistributedDataFilter()
{
}
void MyD3::PrintSelf(ostream& os, vtkIndent indent)
{
this->Superclass::PrintSelf(os,indent);
}
int MyD3::RequestUpdateExtent(vtkInformation *vtkNotUsed(request),
The instructions I gave were for a downstream filter separate from D3. If you
want to modify D3 itself (which sounds like a reasonable good idea for your
purposes) then you will have change the value for UPDATE_NUMBER_OF_GHOST_LEVELS
that the RequestData reads. If you want to go with this appr
Ok thanks again for the advice. Think it's really clear I'm confused
between the "downstream" nomenclature. Do mean just a class that
constructs or takes a D3 as input that I write from scratch outside of vtk?
Or do you mean something totally different? Clearly my understanding of
"it was to inh
By "downstream" I mean a separate filter that is connected to the output of
vtkDistributedDataFilter or further down the output ancestry. In your original
example you had the chain of filters vtkDistributedDataFilter ->
vtkPieceScalars -> vtkDataSetSurfaceFilter. vtkPieceScalars and
vtkDataSe
