Difference between revisions of "VTK/VTK 6 Migration/Removal of SetExtentTranslator"
From KitwarePublic
< VTK
Jump to navigationJump to search
(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...") |
|||
Line 1: | Line 1: | ||
= Removal of SetExtentTranslator and GetExtentTranslator from vtkDataObject = | = 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 [ | VTK 6 introduces a number of backwards-incompatible changes. The reasons behind these changes are described in more detail [[VTK/VTK_6_Migration/Overview]]. 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 == | == Example 1 == |
Revision as of 18:58, 6 April 2012
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 VTK/VTK_6_Migration/Overview. 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
vtkDataObject* dobj = algorithm->GetOutput();
dobj->GetExtentTranslator();
with
vtkStreamingDemandDrivenPipeline::GetExtentTranslator(
algorithm->GetExecutive()->GetOutputPort());
Example 2
vtkDataObject* dobj = algorithm->GetOutput();
dobj->SetExtentTranslator(translator);
with
vtkStreamingDemandDrivenPipeline::SetExtentTranslator(
algorithm->GetExecutive()->GetOutputPort(),
translator);