1. 26 Sep, 2017 2 commits
  2. 17 Apr, 2017 3 commits
    • Ben Boeckel's avatar
      Merge topic 'objimporter_fixes_6.3' into release-6.3 · 00f68944
      Ben Boeckel authored
      * objimporter_fixes_6.3:
        fix issues when importing obj files with windows line endings
        Many fixes to OBJImporter
      00f68944
    • Ken Martin's avatar
      fix issues when importing obj files with windows line endings · 127f54b5
      Ken Martin authored
      Thanks to Pat Marion for tracking this down and providing
      the patch. Handles windows line endings.
      127f54b5
    • Sankhesh Jhaveri's avatar
      Many fixes to OBJImporter · 70ce7300
      Sankhesh Jhaveri authored
      This topic fixes a few issues and adds a test executable
      that can be used to convert obj files to vtp more easily.
      
      The issues fixed are
      
      1) having a map_Kd without a texture name cause a crash
      
      2) having materials in the mtl file that were not used
      resulted in geometry and parts missing from the output
      
      3) having material names with spaces in them caused
      the material not to be recognized
      
      4) some packages use map_kd instead of map_Kd causing
      textures to not be found.
      70ce7300
  3. 20 Feb, 2017 2 commits
  4. 06 Jul, 2016 2 commits
    • David Gobbi's avatar
      BUG 16054: Reduce chance of mistaken swig pointer string. · 66c211a7
      David Gobbi authored
      In the Python wrappers, the vtkDataArray::SetVoidArray() method can take
      two kinds of arguments:
      
      1) a string formatted as a swig pointer "_addr_type" where "addr" is
      the hexadecimal address and "type" is the type, e.g. "p_void".
      
      2) a Python buffer object (any Python object with buffer protocol)
      
      A Python string (in Python 2) is also a buffer object, therefore there
      is some ambiguity.  The use of swig pointers with VTK is exceedingly
      rare, so this fix requires that the string exactly matches the format
      "_addr_p_void" to be interpreted as a swig pointer.
      
      Note that in Python 3, the ambiguity disappears because a string in Py3K
      does not have the buffer protocol.
      66c211a7
    • David Gobbi's avatar
      16130: Fix inconsistency in vtkImageSliceCollection. · a2e13351
      David Gobbi authored
      The Bottom member of vtkCollection was not updated if the added slice
      replaced the previous bottom slice of the collection.  This caused an
      inconsistency in the data structure which could lead to a crash in
      subsequent operations.  I have rewritten the insertion code to reduce
      its complexity.
      a2e13351
  5. 06 Jun, 2016 1 commit
  6. 16 May, 2016 1 commit
  7. 25 Apr, 2016 1 commit
  8. 12 Feb, 2016 1 commit
  9. 11 Feb, 2016 1 commit
  10. 10 Feb, 2016 1 commit
  11. 08 Feb, 2016 1 commit
  12. 04 Feb, 2016 2 commits
  13. 20 Jan, 2016 1 commit
  14. 13 Jan, 2016 1 commit
  15. 18 Dec, 2015 3 commits
  16. 15 Dec, 2015 1 commit
    • Joachim Pouderoux's avatar
      Fix a bug with vtkDelaunay2D. · 57316c29
      Joachim Pouderoux authored
      In a previous patch, a mechanism was added to check edges once
      constrained edges were applied. However, in some cases, this
      check can break some constrained edges.
      This patch make sure to not perform this edge check for triangle
      edges which contains a constrained edge.
      
      (cherry picked from commit ac7a28f9)
      57316c29
  17. 14 Dec, 2015 1 commit
  18. 10 Dec, 2015 1 commit
  19. 09 Dec, 2015 2 commits
  20. 04 Dec, 2015 1 commit
  21. 03 Dec, 2015 1 commit
  22. 30 Nov, 2015 2 commits
  23. 27 Nov, 2015 1 commit
  24. 19 Nov, 2015 3 commits
  25. 18 Nov, 2015 1 commit
  26. 16 Nov, 2015 2 commits
  27. 13 Nov, 2015 1 commit