Hi Luke

Luke Iannini wrote:

i arbitrary use ".", "-" and "_" . IMO a separator in a send/receive name is needed when you use a dollar, and i would welcome a guideline, especially if there is a certification and quality brand for pd-patches :)

but there are so many styles and i don't even know which way to declare an external.

now a bit personal: i don't like $0 :) . It's fine for a namespace within a patch, but I found myself often needing to access something from "outside" so i have to pass $0 around, which is ugly. I much more prefer a global receiver and route everything. so i pass the name of my patch to it's abstractions. abstracions get global receiver with $1 in it which is the motherpatchname. it helps for orientation i.e. look at the window title:

yourabstraction.pd (mother) isn't it better than: yourabstraction.pd (1284)

you can even use it for [sssad $1/vol] without having the $0 making your sssad key into a unusable name. If I have GUI inside the GOP each sliders send and receive name begin with $1. or $1- or $1_ (guideline please!), that makes it possible to hijack the patch from an other patch. Like the midilearn or automator patch can control any slider in this setup.

Franks recommendation UPPERCASE for globals is really neat.

For GUI elements like sliders I've never regret to use a kind of name hierarchy ($1.vol), usually mypatch-myabs-myparameter or mypatch.myabs.myparameter or mypatch_myabs_myparameter or whatever. so you can hijack your channel aux-sender with anything.

but that means you can't open a patch multiple times, no problem for me because i reuse code always with abstractions.

does somebody run 1 patch multiple times? (sounds like fun would you mind and share?)

i look forward to the lazy-vote :)

eni

Programming recommendations

always use [trigger] for 1tomany connections