Loadbangs are "depth first", i.e., loadbangs in abstractions (and subpatches in general) go off before loadbangs in the parent. This is so that abstactions can initialize themselves before receiving messages coming from other loadbangs.
Two loadbangs in the same canvas (window), or in canvases neither of which is a parent of the other, might go off in either order.
cheers Miller
On Tue, Aug 09, 2005 at 09:41:29AM +0200, Frank Barknecht wrote:
Hallo, Tim Blechmann hat gesagt: // Tim Blechmann wrote:
i'm currently thinking about an elegant way to get rid of the problem of ordering loadbangs.
from what i understand, at the moment, there is only the following order of loadbangs: abstractions, subpatches, canvas.
Hm, is this "specified" somewhere? Or is it just "the way it is" currently, similar to the way, two connections of a message outlet are currently handled by creation order, however by specification the order there is undefined?
My practical view to loadbang ordering is simple: The only elegant way to solve the problem is triggers. They make the ordering explicit and printable.
Ciao
Frank Barknecht _ ______footils.org__
_ __latest track: "plak" @ http://footils.org/cms/show/44
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev