@woland thanks for the detailed reply. The analogies are clear, but I do feel they are not super relevant as we are programming video not getting different height people out doors 😀
Jokes aside, again, I do understand the scaling, but I think sticking to rules for the sake of it might not be the best option. I want to suggest a few scenarios where the scaling seems to fail.
FIrst is the router and selector - the system obviously stops here with whatever mechanism is controlling it. If this scaling worked consistently I should be able to connect a counter set to a min of 0 and max of 100 and have the router or selector would switch every 25, but instead it accepts the output of the counter as an absolute value.
But this does scale with the wave generator:
But if I convert the float of the wave generator to an integer, it stops scaling as the design would suggest (the user actor just has a float in and integer out).
This is where scaling between different types seems strange.
Some actors with a variable number of inputs and outputs will update the scaling to match, the keytable actor always has its output max at 255 by default. This one would make more sense to update the scale max to the number of keys. If there are 10 keys there is no way to get to 255. This seems inconsistent with the design, the max should start off reflecting the max value that can be output from that actor. I guess if you set a different max and then change the number of keys there is a decision to make as to whether to force update the max, but if you have done made this change I guess you are ready to adjust it.
I do still feel that the use case for a boolean giving the max and min values by default is so rare that it would make more sense to have these as absolute, but again an absolute value out checkbox on each output would be cool.