hi all,
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.
but having two sub-patches, i can't be sure, which one is loadbanged first. this can be a problem when having abstractions that should be initialized from other abstractions somewhere in pd (not from a parent canvas). thus i'd propose the following: there are basically two ways how abstractions communicate with each other: inlets and receives. i'd propose that every inlet / outlet / receive declares a loadbang function. before this loadbang function has been run, the outlet events are queued (maybe using clock callbacks), then then the behaviour is the same as currently. for the outlets it's more tricky, since they'd have to register a loadbang on the parent canvas.
if someone can think of a more elegant way / has a different opinion, i'd like to hear ...
cheers ..... tim