Meaning, which receive will actually receive the data first? The one that was first connected?

Althougth that is true for local connections, weirdly enough, in non-local connections the last created receive object receives data first.
In local connections the problem can be solved using trigger. A solution for non-local ones doesn't occur to me.

If there is really no workaround on this:
What if a second argument would define the order? (e.g.: [r bala 1], [r bala 2] ... )



alabala


--
ypatios