Fix spread range documentation
This MR updated spread
to match how it is implemented in the OSC handlers, as well as fixes some HelpSource/Examples
.
See SatieOSC-nodeHandlers. A spread
value received via OSC is clipped to the range 0-1, not 0-100 as expected. Also, the spread
value is inverted: 0 becomes 100, and 1 becomes 0.
For the 1.3.1
patch release, I propose that we document the current behaviour as is. For the next minor 1.4.0
, we should decide how we want the spread values to be implemented and make a breaking change.
Edited by Patrick Dupuis