Added IntParam::range() and FloatParam::range()

[rbmj]

This allows calling code e.g. pass a bunch of IntParams to a function that creates widgets - removing the need to create custom widgets for each GUI library and instead use some glue code to generate widgets since now they can determine the correct bounds for a knob/slider from the &IntParam

I'm open to modifying it to return &Range instead of Range... over to you on that API decision

[robbert-vdh]

This allows calling code e.g. pass a bunch of IntParams to a function that creates widgets - removing the need to create custom widgets for each GUI library and instead use some glue code to generate widgets since now they can determine the correct bounds for a knob/slider from the &IntParam

That's part of the reason why most widgets (also in other plugin frameworks) work with normalized parameter values. The unnormalized values typically aren't very useful.

That being said, there's no harm in exposing these ranges on the parameter objects, so may as well.