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 http://WilliamAHuston.blogspot.com -- Facebook http://facebook.com/billhuston -- Twitter http://twitter.com/WilliamAHuston-- Youtube https://www.youtube.com/channel/UCGijK1amWOLglT3YeTyEBNQ?sub_congfirmation=1 Document collections: VirtualPipelines http://TinyURL.com/VirtualPipelines -- BHDCSDimockArchive http://bit.ly/BHDCSDimockArchive Please support my work: TinyURL.com/DonateToBillHuston
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 http://WilliamAHuston.blogspot.com -- Facebook http://facebook.com/billhuston -- Twitter http://twitter.com/WilliamAHuston-- Youtube https://www.youtube.com/channel/UCGijK1amWOLglT3YeTyEBNQ?sub_congfirmation=1 Document collections: VirtualPipelines http://TinyURL.com/VirtualPipelines -- BHDCSDimockArchive http://bit.ly/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
On 04/28/2018 06:57 AM, William Huston wrote:
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. *
it is not. it is the designed behaviour of the iemguis.
however, i don't understand your problem. you simply create a [r $0-FOO] and whenever you click on one of the toggles, they will change state simultaneously *and* will output the current state via the [r $0-FOO] object.
gfmdsar IOhannes
Thanks IOhannes and Tim!
On Sat, Apr 28, 2018, 2:23 AM IOhannes m zmölnig zmoelnig@iem.at wrote:
On 04/28/2018 06:57 AM, William Huston wrote:
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. *
it is not. it is the designed behaviour of the iemguis.
however, i don't understand your problem. you simply create a [r $0-FOO] and whenever you click on one of the toggles, they will change state simultaneously *and* will output the current state via the [r $0-FOO] object.
gfmdsar IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-
IOhannes m zmölnig -
tim vets -
William Huston