Hmm.. how to explain myself.
I have built a project which is expandable... it builds itself through abstractions defined in a table. However, at the centre is a matrix [matrix~ x y z] which needs to scale according to the numbers of abstractions x & y in the project.

I can create (within a patch) the largest matrix that might be required... with all of the string necessary to connect it..... [r inlet_1>$1] and for all of the inlets and outlets, and then open it with it's size defined (x=$1 & y=$2) so that the excess is discarded....

Does anyone know of a better way to achieve this? I could create the required number of [send] and [receive] objects according to the numbers of inlets and outlets.... but is there a way to connect them to the matrix during the creation of the patch?

David.

Dynamic patching messages? It would be hard to keep track of the object indexes though, if I got what you wanna do right..

Hi Alexandros,
Yes, exactly. I wonder if it would be possible outside of PD. The string is I think simple in the patch.... something like:
#X connect 67 0 49 1;
the 67 and 49 must be object numbers and the 0 and 1 connection numbers for the objects. I can predict the object numbers if I am rigorous in the order in which the objects are built in the abstraction, but I cannot see how to write the connections within PureData. I would need to program the opening of the patch in a text editor (once it has been built) and then paste the "#X connect" lines according to my tables. It would keep the abstractions as small as possible, but as the patch is never written out to a file (except maybe as a "temp" file????). I think I need to look at it some other way... I cannot see it at the moment.

David.

Hi,
Never saw your reply, as I didn't get any notification. Anyway, to use the connection message within Pd, you need to send it to a [send] which sends to a patch (or subpatch) where the objects are being created.
For example, if the patch where you create the objects, is called create.pd, then you send [connect 67 0 49 1( to [s pd-create], and you'll see that the object with index 67, will connect its first outlet to the object with index 49, to its second inlet (yes, you got right what this message means).
Maybe you know all this stuff already, but this is what I understood you were looking for.

THANK YOU Alexandros....

It is obvious............... now that you have shown me how (it is always like that of course).

a thousand thank you's...
I will get back to finishing the project now,

David.

WHOOO.... HOOOOOO.....
I don't whooo.... hooooo... very often at my age BUT... I have to share this with anybody out there who didn't know....

[disconnect x x x x ( works just like [connect x x x x ( so I can make and break connections in my abstractions programmatically depending upon outcomes.....

so truly dynamic abstractions.......... WHOOO... HOOOOOOOOO..
(last time, honest)
David.

That's called an epiphany. Enjoy!

This is pretty much amazing. Why didn't we think of it before?