thank you very much for your detailed answer. I had a vague notion that there is a reason for this, why I didn't had the courage to file this as a bug report.

And thanks for bringing back some basic scaling knowledge to my mind. For me a gate was a gate was a gate.

There soon will come a massive calculator clean up to my patches...

best

r

Well, leaving out the issue of the counter automatically changing it's output range (bad design idea on my part -- sorry!) -- the mutable input behaves as I would expect. The mutation happens _only at the moment you connect the link_. It does not continuously update as you change the limits -- in this case, the counter's output. Let me give you an example where this would be important.

1) Connect OSC Listener to Gate input. Range of output and input are both MIN/MAX

2) Click on 'value' output of OSC Listener. Change to min = 0, max = 1\. The 'gate' input ranges are still MIN/MAX

3) Click on 'gate' input of Gate actor. Change range to min = -50, max = 50. 

You now have an OSC Listener that reads an input of 0-1, but that is scaled to a range of -50 to +50 at the Gate input. If I were to subsequently change the range of the OSC Listener output to, let's say, 0.1 - 0.9 (because there is noise at the extremes) then you wouldn't want the Gate input to suddenly change to 0.1 to 0.9\. To me, that would very often lead to unintended consequences.

So the changing of the Counter output "behind your back" is definitely not the right design decision, I believe the functionality of the mutable inputs and outputs behaves as it should.

Best Wishes,

Mark

Cheers