1. 06 Jan, 2016 1 commit
  2. 05 Jan, 2016 1 commit
  3. 04 Jan, 2016 6 commits
  4. 01 Jan, 2016 1 commit
  5. 31 Dec, 2015 2 commits
  6. 30 Dec, 2015 1 commit
  7. 28 Dec, 2015 2 commits
  8. 26 Dec, 2015 1 commit
  9. 23 Dec, 2015 1 commit
    • Cory Quammen's avatar
      Fixed output point arrays problem with vtkContourFilter · 99541b93
      Cory Quammen authored
      The ComputeScalars option adds the array from which the contour was
      computed to the output. vtkContourFilter used to contour by the active
      scalar array in the point data, but now contours by the point data
      array set with vtkAlgorithm::SetInputArrayToProcess(). However, some
      aspects of copying the data are still controlled by which array is
      designated as active. The result is that when the active scalar array
      is not the same as the one named with SetInputArrayToProcess(), the
      active point data array will not be added to the output if the
      ComputeScalars option is off, and the contouring array will be added
      incorrectly.
      
      This problem manifested only when the input data set type was
      vtkUnstructuredGrid or vtkPolyData. Other data types are handled by
      helper classes where arrays are handled correctly. This patch fixes
      the problem by setting the active scalar array in the input data to
      match the input array to process. An existing test for unstructured
      grid input was modified to test the expected behavior and a new test
      for vtkPolyData was added.
      99541b93
  10. 22 Dec, 2015 2 commits
  11. 21 Dec, 2015 7 commits
  12. 20 Dec, 2015 1 commit
  13. 19 Dec, 2015 1 commit
  14. 18 Dec, 2015 13 commits