Technically it seems to be this: they output in reverse creation order. (The
last [receive] you created in the patch will output first.)
Conceptually, imagine an evil demon changing the order in real-time to screw up
your patch. Thwart the demon by using wired connections, trigger, and
subpatches to define order. Only use multiple [receive]s when message order
doesn't matter. (Same with multiple wires fanning out to various objects from
an outlet.)
-Jonathan
>________________________________
>From: Ludwig Maes <[email protected]>
>To: Pd List <[email protected]>
>Sent: Wednesday, August 3, 2011 5:16 PM
>Subject: [PD] pd message order?
>
>
>so standard objects have right to left ordering of outlet processing, but what
>about send and receive for messages? if multiple objects receive for the same
>name, which one gets it first? is there a triggerlike object for messages, or
>should I send multiple messages each with a differentiated tag like s bla1, s
>bla2, s s bla3 even when I send the same message?
>
>_______________________________________________
>[email protected] mailing list
>UNSUBSCRIBE and account-management ->
>http://lists.puredata.info/listinfo/pd-list
>
>
>
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
