Ben Bogart - FMPM/F1999 wrote:
Hello all,
hi!
Anyhow see any reasons why this would not be a good idea?
because it would take you to hell. the main problem is (as i see it) that you really do not know when to trigger the loadbang: immediately after its creation ? (this would be the same as it is now, since you would have no chance to connect anything to the [loadbang] and so the trigger would be void). after you connected something to the [loadbang] ??? why ? actually the [loadbang] does not know about anything connected, so who will have to keep the track ? what if you want to connect more than one objects to the loadbang ? (yes, i know of the [t b b], but maybe not all of you use it all the time) after the patch is finished ???? in true dynamic patch-creation, who knows ? if you are just dynamically loading abstractions with nested [loadbang]s, the problem of not being able to connect the abstraction's outlet to something before the loadbang fires reappears...
the major difference between dynamic patch-creation and loading a patch is, that, when loading (from a file) you know your parent patch before you have to initiate the child, while on dynamic creation the parent you are in "edit"-mode, so your parent is not finished yet (normally, of course, it can be done, but who knows ?)
i have done quite a lot of dynamic patches, and i have dearly wished the loadbang to work inside dynamically loaded abstractions. on having a closer thought i just didn't find a way of doing it properly.
so the easiest thing is, to add an "init"-inlet to your abstraction and trigger it from outside.
mfg.ds.dr IOhannes
Thanks! Ben
B. Bogart