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?
IIRC they'll appear in the order the objects were created.
To be clear I would use a trigger to explicitly order and send to destinations with different (and meaningful names)
In this case the name is best chosen to reflect the intended action, rather than the source. Hope that makes sense.
a.
On Wed, 3 Aug 2011 23:16:38 +0200 Ludwig Maes ludwig.maes@gmail.com wrote:
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?
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 ludwig.maes@gmail.com To: Pd List pd-list@iem.at 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?
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-08-04 00:06, Jonathan Wilkes wrote:
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.)
exactement. that's what i teach my students: don't ever use [receive] if you _might_ depend on execution order.
and then there is iemgut's [oreceive] (which stands for Ordered RECEIVE), where you can specify a priority, so you have control over execution order (it's also in Gem known as [gemreceive])
fgamsdrI IOhannes
-
Andy Farnell -
IOhannes m zmoelnig -
Jonathan Wilkes -
Ludwig Maes