this is more just needing to spooge out my ideas for an object, whether possible is another matter. but feel i need to share with the developers/public and the like to see if this could be done.
i use signals quite a lot, also things like normal data passing and handling. but the one problem with signal data is that it can get very BIIIIG, even with bpatchers and well thought out patches.
the 2 things that have a leg over the msp of max are [prepend] and [route], these 2 have made patching more elegant and looks good, rather than tons of inputs and outputs on abstractions and [patchers], theyre great, we all love them.
my one sole request that i could have and not ask for any other new externals forever would be a [prepend~] and [route~]. so things like HUGE bpatcher inputs and outputs could be a thing of the past.
think that you could just name your signal with a [prepend~] connect into your bpatcher, then you could [route~] that signal to where it needs to go.
the implications to your patches would free up so much landscape and you can see clearly what is plugged to what. patches would look slicker and should work quicker.
anyhow... phew. thats my spooging finished with. i just need to mop up now.