VTK/VTK 6 Migration/Removal of SetExtentTranslator

From KitwarePublic
< VTK
Revision as of 18:58, 6 April 2012 by Berk (talk | contribs) (Created page with "= Removal of SetExtentTranslator and GetExtentTranslator from vtkDataObject = VTK 6 introduces a number of backwards-incompatible changes. The reasons behind these changes are d...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Removal of SetExtentTranslator and GetExtentTranslator from vtkDataObject

VTK 6 introduces a number of backwards-incompatible changes. The reasons behind these changes are described in more detail [here]. One of these changes is the removal of all pipeline related methods from vtkDataObject. Among these methods are SetExtentTranslator() and GetExtentTranslator(). This functionality is still available through vtkStreamingDemandDrivenPipeline.

Example 1

Replace

<source lang="cpp"> vtkDataObject* dobj = algorithm->GetOutput(); dobj->GetExtentTranslator(); </source>

with

<source lang="cpp"> vtkStreamingDemandDrivenPipeline::GetExtentTranslator(

        algorithm->GetExecutive()->GetOutputPort());

</source>

Example 2

<source lang="cpp"> vtkDataObject* dobj = algorithm->GetOutput(); dobj->SetExtentTranslator(translator); </source>

with

<source lang="cpp"> vtkStreamingDemandDrivenPipeline::SetExtentTranslator(

        algorithm->GetExecutive()->GetOutputPort(),
        translator);

</source>