1. 07 Oct, 2015 1 commit
  2. 01 Oct, 2015 2 commits
  3. 28 Sep, 2015 1 commit
  4. 26 Sep, 2015 1 commit
    • Utkarsh Ayachit's avatar
      BUG #15746: Fixes issues with Merge Points in vtkAppendFilter. · 275fc196
      Utkarsh Ayachit authored
      vtkAppendFilter was incorrectly setting the number of tuples in output
      attribute arrays when "Merge Points" was on. It simply accumulated the
      number of points in each of the inputs, which is wrong when the datasets
      had points that get merged. This was resulting in the output array having
      uninitialized elements. Fixed that.
  5. 25 Sep, 2015 8 commits
  6. 24 Sep, 2015 1 commit
  7. 23 Sep, 2015 1 commit
    • David Gobbi's avatar
      Fix classes that broke the "rule of three" · aceabf30
      David Gobbi authored
      The expanded python wrapping identified a few classes that broke
      the rule of three: they defined a custom destructor (indicating that
      they performed some kind of resource management), but did not define
      a custom copy constructor or a custom assignment constructor.  Some
      builds were generating a warning because of the missing methods.
  8. 22 Sep, 2015 1 commit
    • David Gobbi's avatar
      Wrap many more classes with python. · e6f75b9a
      David Gobbi authored
      This makes the python wrappers ignore WRAP_EXCLUDE, and instead use
      the new property WRAP_EXCLUDE_PYTHON that excludes fewer classes.
      The WRAP_SPECIAL flag, which used to act as a whitelist for python,
      has been removed.
      Because this change causes classes to be wrapped in python by default,
      some third-party VTK packages might break until they modify their own
      CMakeLists.txt files to add WRAP_EXCLUDE_PYTHON where necessary.
  9. 18 Sep, 2015 4 commits
  10. 16 Sep, 2015 1 commit
  11. 11 Sep, 2015 14 commits
  12. 04 Sep, 2015 1 commit
    • Cory Quammen's avatar
      Changed warning macro into debug macro · 0e721888
      Cory Quammen authored
      Commit 86f7895b introduced a warning
      if the VOI of the vtkExtractGrid filter is initially outside the whole
      extent of the input data, even though the filter would eventually
      execute correctly when the VOI was updated. Turned this into a debug
  13. 03 Sep, 2015 1 commit
    • Utkarsh Ayachit's avatar
      BUG #14291: Fix segfault when RemoveGhostCells was off. · 880313ba
      Utkarsh Ayachit authored
      vtkExtractCTHPart incorrectly left the GhostCells array on the output
      data (under a different name) when RemoveGhostCells was off. That
      resulted in an array being present on certain ranks and not on other.
      This ended up causing segfault in the data redistribution code in
      ParaView since it expects ranks to have same arrays. Making
      vtkExtractCTHPart remove the GhostCells array when RemoveGhostCells is
      set to true, so that GhostCells won't be removed from the output, but
      the array that flags the ghost cells is.
  14. 02 Sep, 2015 1 commit
  15. 01 Sep, 2015 1 commit
  16. 28 Aug, 2015 1 commit
    • Dan Lipsa's avatar
      BUG #15397: vtkPProbeFilter crash when geometry dataset is distributed. · c0f2e892
      Dan Lipsa authored
      If running in parallel, vtkPProbeFilter assumes that the whole geometry
      dataset (which determines positions to probe) is available on all nodes.
      If that is not the case a crash happened.
      This commit fixes the crash and prints an error message if
      different geometry datsets are available on different nodes.