I think I can't ever change that behavior without breaking thousands of patches. Beware though - if you try to "defer" something using a "delay 0" but if you're sending messages to someone else who's also trying to use delay 0 in the same way, it might be hard to figure out what order it all happens in. The "trigger" mechanism probably scales better to large patches.
cheers Miller
On Wed, Aug 25, 2004 at 10:37:50AM +0200, Tim Blechmann wrote:
Yep, everything is depth-first throughout the Pd message system, except that individual objects (e.g., pipe) can operate FIFOs.
is the current behaviour of |pipe 0| or |delay 0| the intended? at the moment these objects reschedule the messages (and thus solve my problem). on the other hand there are people on this list (e.g. frank), who consider this as being a bug ...
i'm curious if it will be save to use it in further releases of pd or if you intend to change it ... personally, i'd prefer this behaviour in the specifications of these objects since it makes recursive patching _much_ easier ...
cheers... tim
-- mailto:TimBlechmann@gmx.de ICQ: 96771783 http://www.mokabar.tk
After one look at this planet any visitor from outer space would say "I want to see the manager." William S. Burroughs