The convertTo0to1 or convertFrom0to1 don’t make sense on a NormalisableRange as they return/take int.
NormalisableRange::toFloat() would also be a nice addition
i think the idea of NormalisableRange’s template is not to be any numerical type but just float or double
Agreed.
I just found it weird in this case: float normX = NormalisableRange (getBounds().getHorizontalRange()).convertTo0to1(x)
While typing this i realized i could do getBounds().toFloat()
I just saw this. Would it make sense to change
ValueType convertFrom0to1 (ValueType proportion) const noexcept
to
ValueType convertFrom0to1 (FloatType proportion) const noexcept
?
As I understand, it wouldn’t be a breaking change since calling that function with a non-floating-point type doesn’t work anyway. For example, I just made a wonderful slider that can offer you either maximum volume or complete silence.