Le 19/02/2011 20:58, John Harrison a écrit :
Cyrille I just tried your solution and the problem is that all objects sharing the name of the dynamically-created object all get the loadbang message.
yes. you should create them all in the same time, and then send the loadbang. if this is not possible, you can still : -use different name on your object -use argument on the abstraction and send to bang to a [receive loadbang-$1] object inside your abstraction -use initbang -use a [oneshot] object (or similar) after the loadbang
anyway, i think using dynamic creation in real time is bad. imho, it really should be limited for patch creation.
c
On Sat, Feb 19, 2011 at 1:49 PM, Pedro Lopes <pedro.lopes@ist.utl.pt mailto:pedro.lopes@ist.utl.pt> wrote:
>yes, this is known. By known you mean.. Is it on the bug tracker already? When such things are discovered (and by things I mean issues), shouldn't they be documented inside the help patches? It helps a lot those getting inside pd. Best, pedro On Sat, Feb 19, 2011 at 7:44 PM, cyrille henry <ch@chnry.net <mailto:ch@chnry.net>> wrote: hello, yes, this is known. you have to explicitly send the loadbang, like in this patch, using your exemple. (don't know about initbang, i don't use it) c Le 19/02/2011 20:33, John Harrison a écrit : is it correct behavior that loadbang will not be called when it is part of a dynamically created object? See attached. If you load test-do, it will create an instance of test when you click on the message. Test should print loadbang and initbang, but it only prints initbang. -- John _______________________________________________ Pd-list@iem.at <mailto:Pd-list@iem.at> mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list _______________________________________________ Pd-list@iem.at <mailto:Pd-list@iem.at> mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list -- Pedro Lopes (MSc) contact: pedro.lopes@ist.utl.pt <mailto:pedro.lopes@ist.utl.pt> website: http://web.ist.utl.pt/Pedro.Lopes / http://pedrolopesresearch.wordpress.com/ | http://twitter.com/plopesresearch