Ticket #8775 (closed: fixed)
Instrument view minimum colormap scale not accepting user edits
Reported by: | Martyn Gigg | Owned by: | Roman Tolchenov |
---|---|---|---|
Priority: | major | Milestone: | Release 3.2 |
Component: | GUI | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Gesner Passos |
Description
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.
Change History
comment:2 Changed 7 years ago by Roman Tolchenov
- Status changed from new to inprogress
Re #8775. Relaxed the constraints on the colour map limits.
Changeset: 095afe623c514bbcb70f28035232f06c8468f376
comment:3 Changed 7 years ago by Roman Tolchenov
- Status changed from inprogress to verify
- Resolution set to fixed
To test:
- Open the instrument view. The colour map axis with auto-scaling shows actual limits of the data.
- Set the maximum at a value well above the data maximum.
- 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.
comment:4 Changed 7 years ago by Gesner Passos
- Status changed from verify to verifying
- Tester set to Gesner Passos
comment:5 Changed 7 years ago by Gesner Passos
- Status changed from verifying to closed
Merge remote-tracking branch 'origin/bugfix/8775_min_limit_doesnt_change'
Full changeset: 5742a90d3502a28ecedcceba7b839bc174bfa06d