Hi,
I just noticed that using [send] and [return] the "order of connection" seems to work the other way around. basically if I have a numbox connected to a [send FOO] and then I create 2 [return FOO], the last one I created will receive the message first. this seems to be different from what happens when you connect an object to 2 different objects (without using any [trigger] and any "wireless connection"). in this case the first one connected will receive the message first.
is that a bug?
I'm on Pd 0.48.1
cheers,
Mario
On 07/10/2018 08:18 PM, mario buoninfante wrote:
Hi,
I just noticed that using [send] and [return] the "order of connection" seems to work the other way around. basically if I have a numbox connected to a [send FOO] and then I create 2 [return FOO], the last one I created will receive the message first. this seems to be different from what happens when you connect an object to 2 different objects (without using any [trigger] and any "wireless connection"). in this case the first one connected will receive the message first.
is that a bug?
it's a bug to assume anything about the order of execution when it comes to fan-out. fan-outs happen, when you explicitly connect a single (message) outlet to multiple inlets. fan-outs also happen with implicit connections between a single [send] and multiple [receive]s.
the order is undefined (and it's up to the implementation how it eventually turns out; and the implementation is free to change its current behaviour *at will*).
if you must use [send] with multiple [receive]s, you must write your patches in a way to make them resilient with respect to the order of execution.
gfamdsr IOhannes
On 07/10/2018 08:18 PM, mario buoninfante wrote:
Hi,
I just noticed that using [send] and [return] the "order of connection" seems to work the other way around. basically if I have a numbox connected to a [send FOO] and then I create 2 [return FOO], the last one I created will receive the message first. this seems to be different from what happens when you connect an object to 2 different objects (without using any [trigger] and any "wireless connection"). in this case the first one connected will receive the message first.
is that a bug?
it's a bug to assume anything about the order of execution when it comes to fan-out. fan-outs happen, when you explicitly connect a single (message) outlet to multiple inlets. fan-outs also happen with implicit connections between a single [send] and multiple [receive]s.
the order is undefined (and it's up to the implementation how it eventually turns out; and the implementation is free to change its current behaviour *at will*).
if you must use [send] with multiple [receive]s, you must write your patches in a way to make them resilient with respect to the order of execution.
gfamdsr IOhannes