hi !
...
because it would take you to hell.
do you mean max, with its 'newex' -> [thispatcher]? It works...
i have to admit, i do not have any (real) experience with max
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...
why this is a major problem -- why this should make firing of loadbangs inappropriate? (dangerous, misleading?)
no, i just think, it doesn't really do what you want it to do. if i have an abstraction with a [loadbang], i can use it for 2 (and a lot of other) reasons: (now saying very obvious things)
- to initialize objects inside the abstraction (including
sub-abstractions): the loadbang could fire, as soon as the abstraction is instantiated 2. to initialize the parent-patch (via an [outlet]): then the loadbang has to fire after the abstraction is connected to something. in my special cases, this turned out to happen quite often. and i haven't seen a simple solution for this.
are in "edit"-mode, so your parent is not finished yet (normally, of
well... dynamic creation does not cause switching to edit-mode... (besides, this is yet another case of a 'dirty-flag' bug)
well, this was meant in a metaphoric way. although you are not switching to edit-mode, you do edit the patch and thus pd doesn't know, when editing is finished.
mfg.ds.f IOhannes