NothanUmber ·
This is a continuation of this thread.
As I reached a situation where another solution would have been rather complicated (and it didn't look like the devs would implement the tagged datastreams until tommorrow 😉 ) I did a simplified version of the concept with busses until a proper support for a similar concept is available in SM natively. In contrast to the solution that was presented in the other thread this one does only support one tag per data instance and tags are limited to strings. (Shouldn't be a big problem to go for several tags when array support is a little bit more mature (e.g. a sizeoof module would be needed) and in order to support arbitrary data types for the tags one would need a comparator that works on the grey unspecified data types.) Most things should nontheless be possible with that solution as most things (even arrays of tags) can be serialized into a single string.
Have only translated some selected components that could likely be part of algorithms (didn't touch e.g. gui stuff as tags are presumably not too useful there - but the basic concept should be the same). As it's much stupid copy'n'paste work that's not thrilling enough to be done a dozen times I post them here. (*edit* sorry, link had a typo...*edit*) Have only tested a handful of them though so perhaps you should test whether a specific module does what you want before using it somewhere...
Here a cheap example screenshot (as no midi/feedback is involved that could also easily be implemented just with the link order but it should be sufficient to demonstrate the basic concept):
Greetings, NothanUmber
P.S.: "Filter Triggers By Tag" should mean "Filter Data By Tag" as the component is (in contrary to the first idea in the other thread) not limited to triggers of course...