That is why this object's name will change. It will be called "destroysend" because it sends a "bang" when it is destroyed. It is designed for inter patch communication NOT inner patch communication.
After your receive object, simply add a delay message with 0 for time and you should be sure that the whole patch will be deleted by the time the bang makes it out the delay. Tom On 9/4/07, Roman Haefeli <[EMAIL PROTECTED]> wrote: > > On Mon, 2007-09-03 at 13:33 -0400, Mathieu Bouchard wrote: > > [closemsg] gets > > triggered too late for that. On top of this, it gets triggered in the > > middle of deleting a patch, which means you can't rely on the patch > being > > complete and you can't rely on the patch being empty either. > > when does it exactly trigger? is it true, that it depends on creation > time? i made some tests with the help-patch: if [closemsg xx] is created > _before_ [r xx]-[print], then the message gets printed, when closing the > patch. on the other hand, if [closemsg xx] is created _after_ [r > xx]-[print], no message gets printed, when closing the patch. > i'd say, the most desirable behaviour would be, that it 'bang's before > anything is destroyed. this behaviour would ensure, that everything > within the patch itself, that is triggered by [closemsg], would be > executed. as it is now, it is not clearly defined, whether messages get > executed or not. > > roman > > > > > ___________________________________________________________ > Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: > http://mail.yahoo.de > > -- thomas ouellet fredericks, [EMAIL PROTECTED], montreal, canada
_______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
