Instrument view minimum colormap scale not accepting user edits

[Martyn Gigg]

The Instrument View's colour map "minimum" value always resets itself to the minimum value of the current integration time range when I attempt to type in a new value, whether the "Autoscale" box is ticked or not. Typing the value unticks the box as expected. Similar behaviour happens with the Python command inst_view. setColorMapRange(x,y). Changing the integration time only resets the colour map max and min when "autoscale" is ticked, as expected. The maximum value behaves properly. The same behaviour happens whether I choose Linear or Log scales.

[Roman Tolchenov]

Re #8775. Relaxed the constraints on the colour map limits.

Changeset: 095afe623c514bbcb70f28035232f06c8468f376

[Roman Tolchenov]

To test:

1. Open the instrument view. The colour map axis with auto-scaling shows actual limits of the data.
2. Set the maximum at a value well above the data maximum.
3. Set the minimum at a value that is greater than the data maximum but smaller than the scale maximum. The instrument view should allow you to do this.

[Gesner Passos]

Merge remote-tracking branch 'origin/bugfix/8775_min_limit_doesnt_change'

Full changeset: ​5742a90d3502a28ecedcceba7b839bc174bfa06d

[Gesner Passos]

Now you can change the minimum limits, even if it is greater than the real valid minimum. It fulfills what was required. Hence, passed.

[Stuart Campbell]

This ticket has been transferred to github issue ​9619