Hi,
Lets say I have a subpatch with 'graph on parent' option, and, for example, a slider and a toggle button. On the parent patch I can see them. Of course I can click on them, and the subpatch will notice it. I can change the value of slider and read it inside the subpatch. But I cannot connect any wire to this slider, toggle (or even any gui element) to let the parent patch to change it values. It there any way to connect a wire to / from a gui element that is inside a subpatch?
Yes, I could use inlets / outlets for it, but that would really mess everything up, I just want to connect to gui element like that.

Rafał Cieślak

No. The only way to connect wires to them is to use inlets and outlets. Depending on what you are trying to accomplish there may be ways to fake it. For example if your idea was to have a slider that took an input for values and output audio directly to a dac~ you could make a subpatch with an inlet and outlet~, graph on parent, don't display patch name and make the GOP the exact same size as the slider. That way it looks like you are connecting to the inlet and outlet~ or the slider but in actuality they are the inlet and outlet of your abstraction. If it is something else your trying to do please provide some more details and I will try to brainstorm on it.

-Jon

I'm making a 8x8 bangbuttons matrix, witch lights up in a chosen sequence, and I wanted to capture bangs of few of them (diffrent ones on other parent patches, that's why I need to easily connect to all of them) on the parent patch.

you could use [send] and [receive] to communicate with GUI elements, but that leads to a loss of encapsulation unless you're really careful

I am not totally clear on your explanation of why you need to connect to them directly. Is it because you don't want to deal with 64 outlets? If that is the case you could always have one outlet that sends a integer of what button was hit or a list of the x, y position of the button.

-Jon

@ClaudiusMaximus

But if I use several copies of this subpatch at once their [sens]'s will affect all [recieve]'s on the parent.

@ZombieControl

Well.. I think I'll do it as you suggest. That's not exactly what I wanted to achieve, but this seems to be the easiest method, and works well.

Thanks a lot guys

But if I use several copies of this subpatch at once their [sens]'s will affect all [recieve]'s on the parent.

Unless you are careful, and use [myabs $0-someid] and [myabs $0-anotherid] and use $1 inside myabs to set the receive/send names

hey,

not sure i understand what the exact subject is, but some things i do:
if you're going to use various copies of the same subpatch, maybe it's better to make it a seperate abstraction with creation argument as an id (using $1, $2, etc in the ab).

maybe also use a system for all comunications. ex here ...

http://www.pdpatchrepo.info/hurleur/comsystem.pd