Hallo, chun lee hat gesagt: // chun lee wrote:
I think, the elegant solution was to read out the OSC-outlet's output, and then use the output of [OSCroute /*/preset] for setting the radiobutton or whatever is used to display substates. This however would require that the "substate"-messages to [originator] will generate OSC messages as well, which they currently do not.
While I was reading your suggestion and looking at the rrad.tpl patch to see how it would work, I came up with this and it seems to work ok.
Basically, add a [s $2-radiobutton-update] in the [originator] after the [OSCroute /preset]. And then add a [r $0-radiobutton-update] in the [pd save] or connect that straight to the radiobuttons. What do you think?
I don't like that in this case you would have to remember names of send/receive pairs. Paraphrasing something Miller said in Graz: This is too intelligent, we need a stupid solution.
I think, the solution should be to just route all substate changes to the OSC-outlet, then a user of originator can decide on his/her own, how to connect that information. I attached a very simple implementation of this: originator just got onee mor object: [/preset $1( connected to the final [OSCprepend $1], and rrad.tpl as an example then routes this info to set the radio button.
Ciao
Frank Barknecht _ ______footils.org__