Something like max/msp 's object matrixctrl.
that's nice, thank you!
i don't know the matrixctrl object, but could it be, that you have to add 1 to the [r $0_hrange] before it goes into the [pd tables] subpatch, since the radio button bars are 0 based? otherwise the last row will not be processed.
after this, you don't need then to initalize the modulo in the [pd tables] subpatch anymore.
nevertheless, pretty useful abstraction, thanks for sharing!
btw, here's a similar patch but with number boxes instead of toggles and i went another way.
i guess it's more simple, because my approach in naming the sends and receives of the number boxes is based on rows and columns, so i only have 8 sends and 8 receives and i don't work with arrays, so i can completely pass on subpatches without loosing track.
hope you'll like it!
no, i don't use max. i used reaktor before and began with pd in march of this year.
i never coded an object for pd, but it seem that it can be done in C. there are some tut's out in the web about coding pd objects, but i have to confess, i didn't understand it at all. but my skills in C are not even basic, the biggest program i ever coded was "tic tac toe" game for the linux shell, hahaha....
edit: you can find some code examples in the pd help browser in "6. externs".
and here's a tutorial in english language:
Has this matrixctrl-thing been done as an external yet?