Fix issues #21585

When calling vtkSMPVRepresentationProxy::SetScalarBarVisibility with a
`nullptr` view user gets warning following a recent commit. This
development reverts that behavior.

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

This change ensures that the transfer function property on the
representation proxy is up to date.

This change should ensure that the color opacity editor widget is
re-created for changes in the transfer function2D arrays.

This change links the properties exposed on the properties panel with
the color opacity editor properties for 2D transfer functions.
It also ensures that the histogram in the 2D transfer function editor of
the color opacity editor panel is outdated when properties like
useGradientForTransfer2D or ColorArray2Name are changed.

The transfer function manager creates and registers a new 2D transfer
function proxy based on the XML spec with the controller. This makes it
available to both the volume representation and the transfer function
editor. Effectively, this change makes it so that the same transfer
function being edited by the editor is used for mapping by the
representation proxies.

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

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
`pqUseSeparateColorMapReaction`

`vtkContext2DScalarBarActor` needed
enhanced with new attributes `DrawDataRange` and `MinRange` and
`MaxRange`

Fixes #21122

and update it to the new HTG mapper mechanism (split with OGL mapper)

Yohann Bearzi authored Apr 06, 2021 and Charles Gueunet committed Jan 26, 2022

Still in progress

This reverts commit 593d2435.

The commit led to bug #20445.

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.

The change of CALL_SUPERCLASS from const int to macro definition
avoids a clang-tidy "throw expression should throw anonymous temporary
values instead" warning.

Add support for selection of an array and/or array component for
opacity mapping that is distinct from the array used for coloring
mapping.

The volume representations have been augmented with three new
properties:

* 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++
features.

Finally, transfer function range update code was updated to work as
expected when using a separate opacity array/component.

Reworking how directions/modules are laid out.

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.

This adds a checkRepresentedData paramater to GetArrayInformationForColorArray
that enable to check or not in the represented data, instead of always checking in it.

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

Fixes #18304.

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.

The list now includes "NVIDIA IndeX".

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
```
ans
behaviour
cas
dum
initialise
initialisation
lod
nd
ot
pres
wont
```

This checks the number of annotations before showing the scalar bar and
display a warning if it is too high.