On another note about declare, I think it's not a pain in the ass if you're just using it to make it easier when you're sharing with others.

But it's quite a pain to being forced to use it and then every time you want to use a particular external you must do it, save the patch, close it, then re open so you can finally have that external, no matter if you had the library installed. Specially if that is actually unnecessary. I had never seen that in my Pd years, I think it's really weird.

2016-02-16 12:35 GMT-02:00 Alexandre Torres Porres <porres@gmail.com>:

2016-02-16 6:47 GMT-02:00 cyrille henry <ch@chnry.net>:
hello Alexandre,

I don't know where the train~ object came from

howdy, it's from cyclone

the triangle~ is also a problem : i've got one on my computer, that came from nusmuk-audio. you use an other one, with a different sound. Mine did not accept the "lo 0" message.

yep, from cyclone too

if you "declare" the lib it came from, then there are more chances that this patch would load on my computer. If not, at least i would know what lib to download.

Well, I know about the need and purpose of a [declare] object, and I'm not against it or people who want to use it. When I wanna make it explicit I also go like [cyclone/triangle~], works fine as well.

I don't really share that much patches and worry about it, but in the patches I make available for my classes, I do specify the Pd version I'm using, so if you have it, they'll all load.

chances are that even you, in few years will not remember where does triangle~ came from.

I can personally guarantee there's no chance of that happening :) specially because of my involvement with cyclone now, but I also usually remember about other externals from other pd extended libraries as I try to memorize and rely on not too many.

cheers