Difference between revisions of "VTK/VTK 6 Migration/Removal of CopyInformationToPipeline"
From KitwarePublic
< VTK
Jump to navigationJump to search (Created page with "Removal of CopyInformationToPipeline and CopyInformationFromPipeline from vtkDataObject and sub-classes VTK 6 introduces a number of backwards-incompatible changes. The reasons ...") |
|||
| Line 1: | Line 1: | ||
| − | Removal of CopyInformationToPipeline and CopyInformationFromPipeline from vtkDataObject and sub-classes | + | = Removal of CopyInformationToPipeline and CopyInformationFromPipeline from vtkDataObject and sub-classes = |
VTK 6 introduces a number of backwards-incompatible changes. The reasons behind these changes are described in more detail [[VTK/VTK_6_Migration/Overview | here]]. One of these changes is the removal of the VTK 4 compatibility layer. As part of this change, CopyInformationFromPipeline and CopyInformationToPipeline were removed from vtkDataObject and its subclasses. Copying of meta-data is now the responsibility of the executives. | VTK 6 introduces a number of backwards-incompatible changes. The reasons behind these changes are described in more detail [[VTK/VTK_6_Migration/Overview | here]]. One of these changes is the removal of the VTK 4 compatibility layer. As part of this change, CopyInformationFromPipeline and CopyInformationToPipeline were removed from vtkDataObject and its subclasses. Copying of meta-data is now the responsibility of the executives. | ||
Latest revision as of 14:02, 6 April 2012
Removal of CopyInformationToPipeline and CopyInformationFromPipeline from vtkDataObject and sub-classes
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 the VTK 4 compatibility layer. As part of this change, CopyInformationFromPipeline and CopyInformationToPipeline were removed from vtkDataObject and its subclasses. Copying of meta-data is now the responsibility of the executives.
