[PD] plugin~ external

Kim Cascone kim at anechoicmedia.com
Sat Jun 12 01:12:15 CEST 2010

IOhannes m zmölnig wrote:
> Hash: SHA1
> On 06/11/2010 08:50 PM, Kim Cascone wrote:
>> [print] = standard object ships with both Pd-vanilla and extended
>> [gf_print] = print object shipped with the GridFlow libraries and _only_
>> called when
>> [gf_print] is instantiated in a patch
> why would it.
> (i guess that) gf's [print] is meant as a fully compatible [print], with
> some added features.
yes but collision in name space is really confusing for the user

> most users should never notice (unless in a pleasant way).
I noticed the difference in a not so pleasant way :)

> in the specific case here, i consider the behaviour of gf's print to be
> a bug, 
is [print] GridFlow
or is [pd/print] GridFlow
I'm totally confused now
> which should be fixed (just like zexy's pack/unpack).
I'll make a note of this - thanks for the heads-up
> however, i consider the inability of gf's [print] to print everything
> correctly a way less important problem that an object (like plugin~)
> that keeps crashing the entire system.
that crash only happened for me with an old version of the Gem library
and seemed to go away once I compiled the new version and loaded it into 
> and of course what do we make of things like zexy's [tabread4] and
> [wrap] objects? (i just use zexy because i know it well; i'm sure it
> applies to a number of libs)
I have yet to explore the zexy lib
I'm still trying to get [plugin~] sorted out
so I can finish the FOSS chapter on hosting plugins

> fgmasdr
> IOhannes
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> iEYEARECAAYFAkwSvxQACgkQkX2Xpv6ydvSnzACgyDfjr0GD2HW0VfFEuOQLom55
> iocAn2xymReyRFY15iMQIGbKcZvTJU8y
> =50ul

More information about the Pd-list mailing list