[patcherargs] order...
Hi,
A couple of times now I've had the problem of [patcherargs] outputting its default argument after the one I enter in the abstraction's object box. What regulates this, and how to avoid the collision (other than using delays)?
Thanks,
Brian
i have never seen that happen - can you post an example ?
After much consternation, I think this problem might be related to other complications in the patch, not directly about [patcheragrs]. Thanks.