Is there a way to achieve the "segmented cords" as shown in the figure below?
I'm using Plugdata, of course, but I would like to know if one can do that in vanilla Pd with some type of external/plugin.

Thanks!

@blindingSlow Do you mean the bezier/bendy wires? pd-next has them and is just vanilla pd with color themes and an option for bendy wires, although they don't loop around quite like they do in plugdata. pd-next is 1:1 with vanilla otherwise and if you use the default color theme it will be identical to vanilla.

https://github.com/sebshader/pdnext
https://forum.pdpatchrepo.info/topic/10943/a-little-pd-mod

Edit: They might bend around like plugdata on OSX, they will at the very least look nicer than on linux since OSX Tk has antialiasing enabled by default.

@blindingSlow I might be adding nothing new to the post from @oid.
In windows Pd vanilla this works..... curve_cords-plugin.tcl ..... but is not very pretty even with wish86.exe.

and for objects vertically stacked as in your OP it really doesn't work at all....

However, I believe the code in the plugin was lifted directly from Pd-L2Ork. so relied on the Pd-L2Ork GUI.
The code in the plugin is pretty straightforward, and so it might be improved fairly easily for Vanilla?
It looks as though -smooth 1 -splinesteps 36 are not behaving in tcl....... https://www.tcl.tk/man/tcl8.4/TkCmd/canvas.htm#M139 .... but it seems tkinter (part of Python) would need to be installed? I am really unsure about that and I don't see why it should be necessary.
David.

@blindingSlow And I'm sure your example was only meant to show the curved connection, but as an actual patch it overflows the stack because it's an endless feedback loop. Just sayin'

I sometimes use 'nop' as a subpatch or abstraction just to segment connections, but it's not curved of course.

@blindingSlow If @porres's solution is what you meant then you can just use triggerize, select the wire you want to bend and hit ctrl/cmd-t, it will insert a [t a] for message rate wires or a [pd nop~] for audio rate which you can then move as needed with no typing. The message rate [pd nop] might be a little more efficient than a [t a] but either will be fine in the vast majority of situations and will be a non-issue unless you are using a great number of them or have pushed things to the point you need to count cycles.

First of all, thanks everyone! Yu are always so kind in taking the time to answer absolutely everything.
Now let me apologize because I was not very clear on my original post, so here are some corrections and explanations:

• What I'm curious about is if there's any other Pd flavour (or plugin) that will offer the same as Plugdata, which is the ability to bend the cords in order to avoid the almos unavoidable crossing of cords over objects.
• I don't care that much about cords curving or not, either is fine to me.
• The obvious loop is, or at elast was soposed to be, just a joke (-;

@blindingSlow said:

• What I'm curious about is if there's any other Pd flavour (or plugin) that will offer the same as Plugdata

To my knowledge, the tcl/tk "standard" pd interface doesn't and probably will never do that. Pdnext is an offshoot of the tcl/tk interface and only adds bezier-curved cables but not the ability to segment them.

Purr Data might have this, but I don't know.

I'm not aware of any pd front-end interfaces other than the tcl/tk one, Purr Data and PlugData.

hjh

it is important to notice that we have now two forks of Pd with the nw.js gui front: Purr Data and Pd-L2ork, and the latter seems to be more updated and more regularly and actively updated than Purr.

Both don't segment cords to the best of my knowlegde. I'm not 100% sure either, but I could bet on it.