Another little quirk: when dynamically decreasing the number of plugin parameters, for example sending these messages from the device (4.16pre26, default configuration):
Code:
/fxparam/count/32 1
[...]
/fxparam/count/16 1
After the number has decreased, the parameters that are no longer in use (in this example, numbers 17 to 32) are not being 'nulled', i.e. the old names and values may 'stick' around on a (naive) display. It would be nice to have them wiped clean after use.
I haven't yet tested this for dynamically decreasing the other */count/@ patterns, but I suspect the same quirk may appear there too.