Bug Report: NormalisableRange<int> 0to1

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()