List [maximum] + nodes issue and feature request
Hello,
When using [maximum] with nodes, it would be great to know when the knob/slider isn't on any node.
But as [maximum] numbers zero the first item of a list, contrary to nodes which starts at 1, you don't know when you're not on any node.
As you can see on the patch, there is no difference between knob/slider on node 1 and out of all nodes (on no node). This is consistent, but not convenient.
Of course tricky hacks work, but why not allowing [maximum] to count from one instead of zero or to output -1 when all values are zero ?
Try this, move the knob/slider, you'll see what I mean.
Best regards
Roland
Like so? Look up list-processing and the zl-family... Maximum only works on numbers, not lists
add a fifth list element as constant to the maximum-check, then "no match" has its own index.
Thanks a lot Roman.
👍🏻
Such an elegant solution!
Why didn't I think about this. Arghh !
My bad, misread the question... And was also wrong about maximum not taking lists, i guess maximum not outputting a value because of the argument being an integer threw me off.
Nice solution Roman!