Task #11851 (closed)
Opened 6 years ago
Closed 5 years ago
Min/max pixel range with floats
| Reported by: | wmoore | Owned by: | wmoore |
|---|---|---|---|
| Priority: | major | Milestone: | 5.1.0-m2 |
| Component: | Web | Version: | n.a. |
| Keywords: | n.a. | Cc: | cxallan, jamoore, ux@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
See https://github.com/openmicroscopy/openmicroscopy/pull/1902#issuecomment-30747145
Insight doesn't allow the user to enter arbitrary min/max rendering settings, instead restricting them to the actual pixel intensity range. Web displays the pixel intensity range and uses that for the sliders, but it is possible to enter higher values (up to the range supported by pixel type).
Need to align the clients and better inform the user of the range limits.
Change History (4)
comment:1 Changed 6 years ago by jburel
- Cc ux@… added
- Component changed from Insight to Web
- Owner changed from jburel to wmoore
comment:2 Changed 5 years ago by jburel
- Milestone changed from 5.1.0 to 5.1.0-m2
moving to 5.1.0-m2 so we can finalise the work on preview.
Dominik could you check insight?
comment:3 Changed 5 years ago by dlindner
Insight: Slider range == channel type range, but you are allowed to manually set values via the text fields within the pixels type allowed range, which can exceed the channel type range. That's the expected behaviour, isn't it?
There was just a bug, that setting values in the text fields didn't have any effect under certain circumstances, this is fixed by: https://github.com/openmicroscopy/openmicroscopy/pull/3108
comment:4 Changed 5 years ago by jburel
- Resolution set to fixed
- Status changed from new to closed
Fixed during m2 work on preview
This is not correct. Until we have full support for float or 32bit, the behaviour of the web client needs to be adjusted. i.e. Only allow to enter values for the pixels range sets by the RE