Hello, I'm new to the forum, I hope someone here can help...
I succeeded in making a patch with different toggles that behave like radio buttons, so that when one is activated it deactivates the others. In short I send a channel number so that if a message is received with the same channel it is ignored, preventing a loop.
So far so good...

Now I'd like to prevent a toggle to be manually deactivated, so that at all times one toggle is on, while the others are off. I've tried different approaches, but I always end up in a stack overflow, no matter how hard I try... Is there a way?
Thank you!

FYI I don't want to use an actual radio object because these elements will be scattered in different abstractions, working together with send and receive objects.

I think you could have a spigot out of the right outlet of the [select] that goes into a [set 1( message that goes back to the toggle. Set the spigot open when you want the toggle to stay on

@seb-harmonik.ar Thank you, but I'm not sure to understand it correctly... can you elaborate?
I tried as you suggested before, but I'd like it to be automated, so that if the toggle is on and I try to deactivate it directly it stays on, but if it's on and I activate another one it turns off.
This is where I'm at:

I tried to use the left outlet of the first [sel] to set the spigot closed, so that a message comes from the same "channel" it won't pass to the [send] but I couldn't make it work...

I tried this, but it works for half of the times it's ALMOST there!

Oh I misunderstood. You could try opening the spigot from the left outlet of the [sel 1] and closing it before you send the [0 ( (with a [trigger])

maybe like this?

rt.pd
radio-toggle-test.pd

Edit: clean up

@seb-harmonik.ar OMG you did it!
I'm sure I tried it multiple times, but maybe I wasn't using the left [sel 1] inlet...

Thank you SO much! I'm not yet sure WHY it works, I'm going to study it tomorrow, but it actually works!
Oh I can sleep tonight

For future reference here is the working patch:

@lacuna maybe...
I'm sure it works as intended but it's a bit hard for me to understand what's going on...
Thank you for your time! I'm going to study it tomorrow!

Cool glad it worked. I would still do [set 1( instead of [1 ( after the spigot, toggles do take 'set' messages iirc

Here is another way with a few tricks. Following each toggle with a message containing their number allows you to treat them as purely visual and ignore their internal state, no more worry about stack overflows since you are just sending a "set' message.

@oid that's nice and simple. I think you can also ignore the "$1 set 1" message, as the toggle will have been clicked manually, and won't be affected by "$1 set 0". In this case, you have to initiate [f ] with some value that doesn't exist in [route] below it, like -1, to avoid deactivating the first toggle, if this is the one that is being clicked at the very beginning ([f ] will hold 0 without any arguments, so the first time it will be queried, it will send a 0 to the first toggle). Of course that's what you're avoiding with the "$1 set 1" message in your version.
I'm sure you understand all the above, I'm just writing it for anyone else who need clarification.

@alexandros said:

I think you can also ignore the "$1 set 1" message

What do you do if you want to set it remotely with a float? Not an issue if you do not need that feature. I suppose putting the float on its own [t f b] with a [change] before it would not be a bad idea.

And since I forgot to upload the file on the first go around, here it is with the added [inlet]/[outlet], standard radio response to out of range floats, and using single cell radios in place of the toggles so you get the radio look. This is also slightly more efficient since it lets us have a [change] in the ideal spot, unlike the toggles, so less has to be done when it receives the same input but generally this will not really be an issue since not much needs to be done either way.
toggle-radio.pd

And here it is as a useful abstraction, quite handy for interface building. I skimped on all features, I have a full featured version mostly done but I lost interest since this one has all the features I need and it was growing to somewhat ridiculous size for a humble little radio button, one of these days I will get around to finishing it up.

Edit: In my feature culling I accidentally culled one of the most useful features, a symbol to the inlet changes the first argument value. Patch has been updated, will update the rest when time allows.
0radio.pd
0radio-help.pd