1. 26 Oct, 2022 1 commit
  2. 08 Aug, 2022 1 commit
  3. 22 Jul, 2022 1 commit
  4. 06 Jul, 2022 1 commit
    • Yohann Bearzi's avatar
      Initializing the scalar bar when volume rendering · 6136acc0
      Yohann Bearzi authored
      Volume rendering implies setting up a scalar field to render. If nothing
      was selected, the first one in the scalar field list is taken by
      default. However the scalar bar linked to the representation and the
      view was not initialized.
      The scalar bar mechanism in `pqDisplayColorWidget` has been turned into
      a static method that is accessed by `pqDisplayRepresentationWidget`
      when trying to set up the `Volume` representation.
      Fixes #21452
  5. 18 Apr, 2022 12 commits
  6. 08 Mar, 2022 1 commit
    • Yohann Bearzi's avatar
      Scalar Bar Range display bug fix · 140719a5
      Yohann Bearzi authored
      When changing the array to be displayed on a representation that was
      sharing a scalar bar with another representation, the previous array's
      range did not get properly updated. This was because the proxy was still
      stored in the scalar bar widget when it should have been removed. The
      proxy is now removed at update of scalar bar visibility when the lut
      property changed.
      Fixes #21122
  7. 24 Feb, 2022 1 commit
    • Yohann Bearzi's avatar
      New option in the scalar bar to show displayed range values · 3c4cc488
      Yohann Bearzi authored
      The range values of the visible scalar fields can now be displayed on
      the scalar bar.
      To do so, click on `Edit Color Map` icon, then in the new menu, click on
      `Edit color legend properties` icon. If the checkbox `Show Range` is on,
      then the range will be
      printed next to the color bar.
      The range printed is composed of a Min value, and a Max value. The Min
      value (resp. Max value)  is the minimum (resp. maxmimum) value of
      all combined arrays that share the same name and are visible in the view
      (with an open eyeball in the pipeline browser).
      The range values are updated each time
      `vtkSMPVRepresentationProxy::ViewUpdated` is called.
      To handle scalar bar separation, special treatment is needed in
      `vtkContext2DScalarBarActor` needed
      enhanced with new attributes `DrawDataRange` and `MinRange` and
      Fixes #21122
  8. 26 Jan, 2022 3 commits
  9. 22 Sep, 2021 1 commit
  10. 13 Sep, 2021 1 commit
  11. 29 Jun, 2021 1 commit
    • Cory Quammen's avatar
      Enable custom scalar bar title default for given array name · 29c5c57f
      Cory Quammen authored
      Settings JSON configuration files can now specify default scalar bar
      titles for arrays of specific names. In a settings JSON file, a
      `<custom title> `for `<array name>` can be specified with the
      following JSON structure:
        "array_lookup_tables" :
          "<array name>" :
            "Title" : "<custom title>"
      Custom titles can only be read from JSON - this change does not
      include a mechanism to save custom titles from ParaView.
  12. 31 Mar, 2021 1 commit
  13. 23 Feb, 2021 1 commit
  14. 07 Jan, 2021 1 commit
  15. 29 Jun, 2020 1 commit
    • Cory Quammen's avatar
      Support specifying a separate opacity array for volume rendering · 6e1c4c7b
      Cory Quammen authored
      Add support for selection of an array and/or array component for
      opacity mapping that is distinct from the array used for coloring
      The volume representations have been augmented with three new
      * UseSeparateOpacityArray - indicate when a separate opacity array
        is to be used.
      * OpacityArrayName - the array to use for opacity mapping
      * OpacityArrayFieldAssociation - the field association of the array
      * OpacityArrayComponent - the component of the opacity array to use
        for opacity mapping
      When enabled, the volume representations assemble a two-component data
      array from the color array and selected opacity array to hand to the
      volume mappers, some of which support opacity mapping via a
      two-component arrays. The volume representations were refactored to
      move common code into a base class and take advantage of modern C++
      Finally, transfer function range update code was updated to work as
      expected when using a separate opacity array/component.
  16. 03 Feb, 2020 1 commit
  17. 07 Jan, 2020 1 commit
  18. 21 Sep, 2019 1 commit
    • Cory Quammen's avatar
      Handle array associations of type vtkDataObject::POINT_THEN_CELL · f0f41715
      Cory Quammen authored
      Previously, if the array association of the color array was set to
      POINT_THEN_CELL, the array information could not be found because no
      checking of point nor cell data was done. Now, handle this association
      type manually, checking first whether there is a point array with the
      given name then checking whether this is a cell array with the name.
  19. 10 Sep, 2019 1 commit
  20. 15 Aug, 2019 1 commit
  21. 10 May, 2019 1 commit
    • Mathieu Westphal's avatar
      Remove usage of GetDomain(name) · 9fb6d76f
      Mathieu Westphal authored
      This remove usages of GetDomain(name) and replaces them by FindDomain<class>()
      or FindDomain("class") in python.
      This also transform usages of FindDomain("class") into FindDomain<class>()
      This also add support for StringListDomain in python
  22. 04 Sep, 2018 1 commit
  23. 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.
  24. 24 Feb, 2018 1 commit
  25. 07 Feb, 2018 1 commit
  26. 30 Jan, 2018 1 commit
    • luz paz's avatar
      Misc. typos · 5bff56a1
      luz paz authored
      Some are user-facing and some aren't user-facing. Found via `codespell -q 3 -D ~/Documents/diff-experiment/dictionary.txt --skip="./ThirdParty,./Qt" -I ../paraview-whitelist.txt`
      whitelist contents were
  27. 10 Jan, 2018 1 commit