raytracer

I have a BPatcher. The BPatcher uses several loadbang objects to initialize it's internal state. When I copy the BPatcher the loadbang objects don't fire, therefore the new copied BPatcher doesn't work correctly. How do I force the new copied BPatcher to initialize it's state? 

copy-bpatcher-loadbangs-dont-fire-how-to-initialize

if you send a (loadbang) message to [thispatcher], it will make all loadbangs bang. It works for subpatchers, should work for bpatchers.

In my experience, [loadbang] objects work just fine when the bpatcher is "loaded" (i.e., instantiated as part of a patch being opened). When you copy/past an object, or instantiate as part of building a patch, then they don't fire.

Are you really sure that the loadbangs aren't firing when you save your patch, close it, and then open it? It should work.

The behavior should also be documented somewhere. Can't say I remember exactly where, sorry.

Are you really sure that the loadbangs aren't firing when you save your patch, close it, and then open it? It should work. 

The behavior should also be documented somewhere. Can't say I remember exactly where, sorry.


Yes, the [LoadBang] objects all fire when the patch is saved and reloaded. That part is fine. They don't fire when contained in a BPatcher which has been copied. How do I initialize the internal state of a BPatcher when copying it?

Well, you can always go into your bpatcher (after you've copied-and-pasted it into your main patch) and double-click on the [loadbang] object(s). I seem to recall that [loadbang] responds to a double-click by sending a bang out its outlet.

Possibly not enormously satisfying. Given that, in theory, you only do the copy-and-paste creation thing once and open the file lots and lots of times, this may, however, not be all that painful.

is that not good enough to just have to send a loadbang message to a thispatcher object in your parent patch ?.. if not, you might want to use a complicated trick like having a [metro 1 @active 1] [onebang 1] [loadbangs] with a 0 going back to the metro

Thanks Vichug! That does it. Are there any drawbacks to the [metro 1 @active 1] trick?

hm, apart from this beeing quite inelegant, i don't see...

Having to manually fire bangs to trigger patch initialization also seems inelegant as well. An inelegant but automatic method seems preferable to me but I'm a newbie.

Unless I'm misunderstanding something, this is only an issue when you're building a patch. Rewriting a patch to deal with a once-in-it's-lifetime issue seems somehow more inelegant than just manually double-clicking once. But maybe I'm missing something.

Copy BPatcher - LoadBangs don't fire - how to initialize?