I couldn't get Gridflow to work on any of my computers running different versions of windows (Win 7, 32 or 64 bit) and pd 0.43 (either vanilla or extended) whether or not there is a pd 0.42 install on the same computer and with similar binaries.
I think there is some incompatibility at the moment between the pd 0.43 and gridflow. I wrote Mathieu about this a while ago.

pob


On 26/04/2011 15:42, IOhannes m zmoelnig wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2011-04-26 15:23, yvan volochine wrote:

salut Matthieu

another question:

is there a way to force gridflow external to load from a specified path?

ie: I'm trying to setup pd-vanilla wth gridflow-9.13 where the user
already has pd-extended with gridflow-9.12.

(don't ask me why =)

gridflow.pd_linux (9.12) is in ~/pd-externals/gridflow
gridflow.pd_linux (9.13) is in ~/pd-vanilla-externals/gridflow-9.13

problem is that pd -lib gridflow (with the new path to 9.13) still loads
the one from pd-externals (9.12) although ~/pd-externals/gridflow is
*not* in his path.

is there any workaround to this ?

~/pd-externals/ is _always_ in the path.
you might be able to turn this off, by specifying "-nostdpath", though
this will also turn off searching of .../pd/extra/

anyhow, if you add ~/pd-vanilla-externals/gridflow-9.13 to your search
paths (e.g. using the "-path" flag) , then the gridflow found therein
should take precedence over the one in ~/pd-externals/

fgmasdr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEUEARECAAYFAk22y9kACgkQkX2Xpv6ydvQlqACg1zVeI++LdMvTsCpQeDupfWIy
KaMAlR113eCpUS+k8dVmc6dx+YQMLqI=
=tuB1
-----END PGP SIGNATURE-----

-- 


~    Pierre-Olivier Boulant     ~
-o-     www.puffskydd.net     -o-
~   www.flickr.com/pob31/sets   ~
-o-    www.lepixophone.net    -o-