Hi folks, I'm not sure if I'm understanding the externals tutorial properly. It seems to me that it is saying that one cannot make a generic inlet past the first one, as in something that passes any incoming message to the same handler as an array of atoms. Is that the case or am I totally misunderstanding that? And if it's not the case, if someone could tell me how to make the equivalent of class_addanything happen for other inlets than the first, that would be lovely.
thanks! iain
And follow up, if there is a way to make a generic handler for right hand inlets, is there also a way to find out on which inlet the message came in?
thanks
On Tue, Dec 7, 2021 at 5:57 PM Iain Duncan iainduncanlists@gmail.com wrote:
Hi folks, I'm not sure if I'm understanding the externals tutorial properly. It seems to me that it is saying that one cannot make a generic inlet past the first one, as in something that passes any incoming message to the same handler as an array of atoms. Is that the case or am I totally misunderstanding that? And if it's not the case, if someone could tell me how to make the equivalent of class_addanything happen for other inlets than the first, that would be lovely.
thanks! iain
Am 8. Dezember 2021 03:52:00 MEZ schrieb Iain Duncan iainduncanlists@gmail.com:
And follow up, if there is a way to make a generic handler for right hand inlets, is there also a way to find out on which inlet the message came in?
You basically need to create a "proxy" object with a single generic inlet. The proxy object is not displayed (but its inlet is attached to and displayed on) the parent object. It also holds a handle to the parent (so it can forward whatever it receives) and probably it's own ID (so it can identify itself)
just grep for 'proxy's 😋
mfg.sfg.jfd IOhannes
great, thanks very much.
On Tue, Dec 7, 2021 at 10:38 PM IOhannes m zmölnig zmoelnig@iem.at wrote:
Am 8. Dezember 2021 03:52:00 MEZ schrieb Iain Duncan < iainduncanlists@gmail.com>:
And follow up, if there is a way to make a generic handler for right hand inlets, is there also a way to find out on which inlet the message came
in?
You basically need to create a "proxy" object with a single generic inlet. The proxy object is not displayed (but its inlet is attached to and displayed on) the parent object. It also holds a handle to the parent (so it can forward whatever it receives) and probably it's own ID (so it can identify itself)
just grep for 'proxy's 😋
mfg.sfg.jfd IOhannes
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
-
Iain Duncan -
IOhannes m zmölnig