You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we should think about adding the very basic features (that are more complex in this context) of displaying a pixels intensity and auto brightness adjustment to BDV. Happy to discuss and contribute!
The text was updated successfully, but these errors were encountered:
This reminded me of this issue , because the user will have to navigate larger value ranges when supporting more data types.
Auto-contrast UI
What about adding an option for auto-contrast somewhere here?
Maybe add set range auto?
Pixel values UI
Two suggestions:
Add value next to name, current, active, color
Make a new card, called Sources pixel values, where you repeat all the source names
Maybe the second approach could have the advantage that if one hides this card, the code would know that it does not have to fetch the pixel values (in case that is expensive).
range: the current min max values of the Converter bounds: the min and max limits of the UI sliders
For datatypes like uint64 it is, in my view, not trivial to set the bounds such that the user can still sensibly use them.
In MoBIE we have thus implemented some logic that computes the bounds given the current range, happy to discuss this.
Hi, we should think about adding the very basic features (that are more complex in this context) of displaying a pixels intensity and auto brightness adjustment to BDV. Happy to discuss and contribute!
The text was updated successfully, but these errors were encountered: