Mathieu,
I was imagining rather a single send/receive pair messing around with execution order of data entering at once. Thanks a bunch though. -- David Shimamoto > On Wed, 9 Jul 2008, PSPunch wrote: > >> I've never noticed send/receive causing unpredictable execution order. >> Can someone show me an example of under what circumstances this occurs >> so I can avoid future head aches? > > all cases. the receivers are ordered in the order that they are created. > if you are currently editing a patch, this is likely to be different > from the order that it will be when you will reload the patch. the only > way to change the order is to recreate the receivers in the correct > order, but really, you should seek a more transparent way of doing > things. For example, if [r $0-stuff] has to be received in two distinct > phases, make a splitter that uses a [t a a] from [r $0-stuff] to [s > $0-stuff-1] and [s $0-stuff-2] so that all receivers that need the > information early use $0-stuff-1 and the ones that need it late use > $0-stuff-2. > > _ _ __ ___ _____ ________ _____________ _____________________ ... > | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
