hello, it's usually done in a patch by using [switch~]
best
----- "Ivica Ico Bukvic" ico@vt.edu a écrit :
Hi all,
I guess subject says it all. For the sake of efficiency I am hoping to detect whether an inlet is connected to anything and if so to perform its signal-based operations. Otherwise, it should remain dormant. Is there anything in the existing API that allows for this?
Many thanks!
Ico
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
----- "Ivica Ico Bukvic" ico@vt.edu a écrit :
I guess subject says it all. For the sake of efficiency I am hoping to detect whether an inlet is connected to anything and if so to perform its signal-based operations. Otherwise, it should remain dormant. Is there anything in the existing API that allows for this?
[gf/lol] does look at the way that an abstraction-instance is being patched, so that it can do automatic repositioning of all objects connected to the rightmost inlet, or hiding wires, or drawing segmented wires, etc.
It's the closest thing I can think about. It's currently used by [doc_m] and [doc_also]. In those cases, those are only message-outlets that aren't even used for carrying any messages at all, but you could use it in a different way.
http://gridflow.ca/help/gf/lol-help.html http://gridflow.ca/gallery/%23range-help-edit.png http://gridflow.ca/help/doc_also-help.html
This could be the basis for coding an external that does what you want.
(ps: I am not on pd-dev)
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
On Mon, 2010-12-27 at 10:04 -0500, Mathieu Bouchard wrote:
----- "Ivica Ico Bukvic" ico@vt.edu a écrit :
I guess subject says it all. For the sake of efficiency I am hoping to detect whether an inlet is connected to anything and if so to perform its signal-based operations. Otherwise, it should remain dormant. Is there anything in the existing API that allows for this?
[gf/lol] does look at the way that an abstraction-instance is being patched, so that it can do automatic repositioning of all objects connected to the rightmost inlet, or hiding wires, or drawing segmented wires, etc.
It's the closest thing I can think about. It's currently used by [doc_m] and [doc_also]. In those cases, those are only message-outlets that aren't even used for carrying any messages at all, but you could use it in a different way.
http://gridflow.ca/help/gf/lol-help.html http://gridflow.ca/gallery/%23range-help-edit.png http://gridflow.ca/help/doc_also-help.html
This could be the basis for coding an external that does what you want.
(ps: I am not on pd-dev)
Many thanks Mathieu for the info. I will investigate further. Just to clarify, I am trying to achieve this from the external source file, not the Pd patch.
Best wishes,
Ico
On Mon, 27 Dec 2010, Ivica Ico Bukvic wrote:
Many thanks Mathieu for the info. I will investigate further. Just to clarify, I am trying to achieve this from the external source file, not the Pd patch.
What is this clarification for ? (what does it change, anyway ?)
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
On Mon, 2010-12-27 at 13:12 -0500, Mathieu Bouchard wrote:
On Mon, 27 Dec 2010, Ivica Ico Bukvic wrote:
Many thanks Mathieu for the info. I will investigate further. Just to clarify, I am trying to achieve this from the external source file, not the Pd patch.
What is this clarification for ? (what does it change, anyway ?)
It is more in respect to other advice I've gotten so far that deal with pd-patch-side implementation, rather than dealing with fundamental way how array works and registers changes when mouse click'n'drag is altering its content. Just trying to be economical with my replies :-)
On 12/27/2010 04:04 PM, Mathieu Bouchard wrote:
----- "Ivica Ico Bukvic" ico@vt.edu a écrit :
I guess subject says it all. For the sake of efficiency I am hoping to detect whether an inlet is connected to anything and if so to perform its signal-based operations. Otherwise, it should remain dormant. Is there anything in the existing API that allows for this?
[gf/lol] does look at the way that an abstraction-instance is being
and of course there is iemgut's [canvasconnections]
(ps: I am not on pd-dev)
which reminds me: ico, i would very much appreciate it, if you could send your emails either to pd-list or pd-dev. usually the destinction is quite simple: if the problem involves a compiler post it to pd-dev; if it is not, post it to pd-list; i don't think that matju's attitudes towards pd-dev justify for 400 people getting the same mail twice. you could as well post mails to pd-dev and matju (rather than pd-list), or only pd-list (personally i think it's less annoying to get the mail on the wrong channel than on the right channel and on the wrong channel)
fgamsrd IOhannes
On Mon, 2010-12-27 at 13:53 +0100, patko wrote:
hello, it's usually done in a patch by using [switch~]
best
Thank you for the reply. This is however a patch-level control, rather than per-object control, correct? Is there a way to do this inside the object itself?