The other approaches are interesting too - for the way I patch things though, I do think mine's quicker... ie. with this abstraction I don't have to do any typing. I like the new version too, although it would have taken me longer to debug and correctly deploy Frank's version.
The arrays may be unnecessary in one sense, and yet as someone with a little programming background, it's quicker for me to conceptualize a design that uses an array. If I went for Frank's approach I'm sure it would have taken me twice as long (but we know Frank is the guru when it comes to using lists!). I see how helpful lists are, but I haven't 100% internalized the list operations and all the list-abs that are available, as opposed to other PD objects.\
Thanks for sharing, everyone.
~David
Hallo,
padawan12 hat gesagt: // padawan12 wrote:
> Cool. I was struggling with a mutex switch until Frank put me right
> with a diagonal message matrix. I like the use of the array, but I
> cant help thinking, is the intermediate storage really needed?
> Couldn't it be done in two operations, zero everything and then
> just route the 1 to the channel that should be on?
This would work as well, e.g. as in attached construct. You can test
with the previous patch by David.
Ciao
--
Frank Barknecht _ ______footils.org_ __goto10.org__
_______________________________________________
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list