1. 18 May, 2018 2 commits
  2. 04 May, 2018 1 commit
  3. 30 Apr, 2018 1 commit
  4. 27 Apr, 2018 1 commit
  5. 25 Apr, 2018 1 commit
  6. 23 Apr, 2018 1 commit
  7. 09 Apr, 2018 8 commits
  8. 05 Apr, 2018 1 commit
  9. 02 Apr, 2018 1 commit
  10. 30 Mar, 2018 1 commit
  11. 18 Mar, 2018 1 commit
  12. 09 Mar, 2018 1 commit
  13. 08 Mar, 2018 1 commit
  14. 02 Mar, 2018 2 commits
  15. 01 Mar, 2018 1 commit
    • Andrew Bauer's avatar
      Fixing loading Python state · b4485841
      Andrew Bauer authored
      Also adding in a test that loads a Python state from the paraview
      --state command line option as well as checking on some of the
      backwards compatibility functionality for Python state.
      
      Fixes #18012.
      b4485841
  16. 28 Feb, 2018 1 commit
    • Michael Migliore's avatar
      Add a new checkbox in Volume representation to avoid confusion with MapScalars · 2352686f
      Michael Migliore authored
      When volume representation is selected and **Map Scalars** and selected data
      array has 2 or 4 components, a new property called **Mutliple Components Mapping**
      is available.
      
      When this new feature is enabled:
      * for a two-components array, the first component is mapped to the color, the
        second component is mapped to the opacity.
      * for a four-components array, the first, second and third components are used
        as RGB values and the fourth component is mapped to the opacity.
      
      Note that:
      * this feature is only available when **MapScalars** is *ON* ;
      * this feature forces **Use Separate Color Map** ;
      * it scales the color and the opacity range with the correct component.
      2352686f
  17. 21 Feb, 2018 1 commit
  18. 20 Feb, 2018 2 commits
  19. 16 Feb, 2018 2 commits
  20. 15 Feb, 2018 1 commit
  21. 10 Feb, 2018 2 commits
  22. 08 Feb, 2018 1 commit
  23. 07 Feb, 2018 2 commits
  24. 25 Jan, 2018 2 commits
  25. 24 Jan, 2018 1 commit
    • Utkarsh Ayachit's avatar
      Avoid using obsolete data bounds. · 1820718e
      Utkarsh Ayachit authored
      Due to the disconnect between the representation and its mapper, when
      `vtkPVRenderView::SynchronizeGeometryBounds` is called, there was a
      potential that we'd end up using bounds from obsolete data. That was
      causing #17941.
      
      This fixes #17941 by ensuring that vtkPVDataDeliveryManager cleans any
      obsolete datasets when a new one is provided to it by the
      representation.
      1820718e
  26. 23 Jan, 2018 1 commit