why oh why would the default values for min and max of an IOBox integer be wanted so low?
I’ve been doing lots with pixel precise rendering for UIs and using integer is great except when using an HD display and setting 0,0 to a corner I always hit the limit of a IOBox integer. I then have to change it manually everytime. I sometime have to follow down through subpatches if connected multiply integer IOBoxes and change their defaults too.
i’d rather not change min/max when switching modes. say you have set min/max to something specific and then on switching modes it always jumps do defaults…i’d say thats not the desired behavior.
true, we’ll have to live with 0/0 as default for the slider but i think thats understandable…
you know what…all different again. we found that those changes mentioned above caused too many troubles. so now we decided to just go with changing the min/max default from -1000/1000 to a much larger number thus hopefully reducing the times those are annoying to a negligible amount without causing further unrelated problems. test in latest alphas.