hi,
one quick and dirty way is to make a dummy abstraction with proper number and types of inlets and outlets in it (and nothing more). Call it nop.pd, and replace [<obj> <args>] with [nop <obj> <args>].
If there is a need to disable many objects with varying interfaces, then designing a clean naming scheme for nop abstractions may become a challenge.
But designing a builtin method of disabling arbitrary objects (that are already created and patched) would be a much bigger challenge...
Krzysztof
Larry Troxler wrote: ...
Thus, I thought it would be neat if there were a way in PD to "comment out" or disable certain objects in the patch. Of course, I can just type some garbage in front of the object names, for those objects that I wish to disable (that's what I'm doing now), but then all the connections are lost and I need to remember how to redo them the next time I enable the object.
So, I was thinking that it would be nice if there were a better way to disable objects, where the connections would remain, only the object would be disabled. I'm not talking about DSP processes only, but also disabling the the message passing.
...