When the instrument view is modified so that the color map is updated,
it makes sure the scale of the color map shown in the render tab is
updated to the new values too.

In the Draw tab of the instrument viewer, when grouping by pixel or
bank, the infotext at the bottom informs the user of what is selected,
so there is at least some info on what is going on.

Use the storeDetectorMask option to actually manage the masking/ROI.
Cleaner and more efficient.

When picking a single pixel, 2 behaviours are possible : either it's for
masking, and then the picked pixel must be masked on screen immediately,
or it's for picking and then nothing happens to the instrument.
Separating the signals allows for calling the appropriate slot depending
on the current tab.

When computing the vector containing the detectors to ROI, in the
case of pixel and tube, erase elements after using remove, both to
remove a warning and because it is not supposed to work without this
change, even though it did.

It is now similar to the one from the Pick tab.

Adds the possibility to select and group individual pixel and tube.
HOWEVER due to these selections being dependent of the detector, contrary
to every other shape used for masking etc, the selection cannot be
printed on screen, as it would require to create a shape that follows
the detector if it is moved and is rendered using the correct
perspective.
Moreover, contrary to what happens with masking and ROIing, there are
two options for grouping, which means the operation cannot be applied
immediatly on click in this case.
Since this means that a) the user should input after doing their selection
and b) this selection cannot be shown to the user on the instrument
view, the compromise solution was to only take into account and store
the last tube or pixel selected for grouping. In other words, the user
can only sum or extract the last pixel / tube they selected.

The user's interactions are now taken into account (and dynamically)
when the "center" field is edited (for a sector).

On the mask tab of the instrument view, when the user inputs a value in
one the field, the view is now updated on validation of this value (i.e.
when the user clicks outside the field or hits Enter), whereas before,
the user needed to hover over the instrument view to see the changes
take effect, which was illogical.

Also, when there is a correction on the value entered (for example a
negative value for a positive-only field), the value corrected is
immediatly showed, instead of waiting for the user to deselect-reselect
the shape.

- Add a proper shortcut
- Fix the bounding box not following the sector when moved, but updating
it
- Set new endAngle at creation
- Fix a bug where the topLeft corner drag was mismanaged due to a bad
variable
- Better check for angles and radii values

Refactor redondant parts of the code and modify some default values to
be more convenient for the user.

Even if it does probably not make much sense by itself, the ROI option
now behave similarly the pixel and tube picking that it does from the
other buttons.

Create the link between the mask interface and the 2D sector shape
object, and thus adds the possibility to create one such shape.

An uneeded cast from size_t to unsigned long was causing the windows
build to fail.

On the instrument viewer's draw interface, it adds a button in charge
of masking complete tubes or banks.

After the user has picked a single pixel, contrary to other masking
options, editing the shape is not possible and thus the default
behavior should be to stay on this option.

Adds the option to mask a single pixel of a detector, similarly to the pick
option.

Giovanni Di Siena authored Mar 31, 2020 and Gigg, Martyn Anthony committed Apr 07, 2020

In places other substitutions have been made, e.g
Clang does not yet specialize std::shared_ptr for T[]. Vector
has been used instead. The operator[] methods were incorrectly
marked const but returning a non-const reference - this has been fixed.
Refs #25842

Replaced in tests and code with AlgorithmManager::create

Not expecting to pass all tests yet, just checkpointing

Also updated class_maker.py

Project saving does not yet exist in newer builds and
will not take the same form.