1. 18 Jul, 2018 1 commit
  2. 16 Jul, 2018 1 commit
  3. 12 Jul, 2018 2 commits
  4. 11 Jul, 2018 1 commit
  5. 06 Jul, 2018 1 commit
  6. 11 May, 2018 1 commit
  7. 10 May, 2018 20 commits
  8. 08 May, 2018 1 commit
    • David Gobbi's avatar
      Backport 'reslicemapper-border' to release branch. · 508c2ada
      David Gobbi authored
      When MultiSamples are used in VTK (which is the default on Windows
      and Linux), a thin border appeared at the edge of the image if the
      the image pixel values were not zero at the edge.  The thin border
      is the result of the zero 'Background' value of vtkImageReslice.
      All of the "Background" pixels produced by vtkImageReslice are
      supposed to map to beyond edges of the polygon used to render the
      image texture.  However, MultiSamples causes the edge to be soft,
      and the coloring of these background pixels bleeds into the edge
      of the polygon.
      
      The solution is to tell vtkImageReslice to add a bit more edge
      tolerance when clamping its interpolation coordinates.  This moves
      the 'Background' beyond the edge of the polygon, so that these
      background pixels no longer bleed into view.
      508c2ada
  9. 04 May, 2018 2 commits
  10. 01 May, 2018 1 commit
  11. 27 Apr, 2018 1 commit
  12. 26 Apr, 2018 1 commit
  13. 27 Mar, 2018 1 commit
  14. 26 Mar, 2018 1 commit
    • Cory Quammen's avatar
      Fix out-of-bounds memory write · 77183b27
      Cory Quammen authored
      An out-of-bounds memory write could occur in GetSingleLoop() when the
      condition (pointCells->GetNumberOfIds() < 2). GetSingleLoop() adds a
      line cell to complete a loop in this case, but that fact was not
      accounted for in the caller when allocating the argument for the
      lineBool array. Fixed that, and cleaned up the code by using a
      std::vector instead of an array. Finally, added a test that exercises
      the condition to make sure it is tested.
      77183b27
  15. 17 Mar, 2018 1 commit
    • David Gobbi's avatar
      17265: Fix OpenGL2 vtkImageResliceMapper OOB issue · fd6b906b
      David Gobbi authored
      For OpenGL2, the vtkOpenGLImageSliceMapper:RenderPolygon was being
      called even if the slice specified by vtkImageResliceMapper was
      beyond the volume bounds.  This caused a regression: specifically,
      when the slice moved out-of-bounds the old polygon would be reused
      even though no polygon should be displayed at all.  The fix is for
      RenderPolygon to return early if no polygon should be displayed.
      
      Closes #17265
      fd6b906b
  16. 12 Mar, 2018 1 commit
  17. 11 Mar, 2018 1 commit
  18. 10 Mar, 2018 1 commit
  19. 09 Mar, 2018 1 commit