If I understood you correctly, this is how I would do it.

[r gang]
|
[set $1(
|
[tgl]
|
[s gang]

You can then copy as many of these as you like, and [r gang] will receive 0 or 1 once each time you click either of the toggles.
gr,
Tim


2018-04-28 6:57 GMT+02:00 William Huston <williamahuston@gmail.com>:
I'm trying to make a Ganged Toggle.
(but this also could apply to other graphical elements
like hsl or vsl etc)

I want to have #1 little orange [tgl] inside the
graph-on-parent control window,
and have a similar #2 little orange [tgl] inside the patch.

I want to be able to click on either one. This
should trigger a state change in the other.
 
I want them to function as one logical element,
with two different gui locations.

Right now, let's say I set both [tgl]'s
to both send and receive on $0-FOO.

This seems to work, as both GUI elements
track as I would expect.

However, if we name the master as being the one that I click,
then I see that the slave tgl does not transmit on its outlet.

This seems like a bug to me.

If this is expected behavior, or a necessary limitation, or
a bad practice....

then how else can I accomplish a "Ganged Toggle"
(e.g. could be hsl, etc.) with minimal logic?

Thanks
BH



--
William Huston:  WilliamAHuston@gmail.com
Binghamton NY

Public Service Mapping / Videography / Research
Blog -- Facebook -- Twitter  -- Youtube
Document collections: VirtualPipelines -- BHDCSDimockArchive
Please support my work: TinyURL.com/DonateToBillHuston



_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list