[PD-dev] saving preset pools in the parent path, rather than the abstraction path?
ix
ix at replic.net
Thu Nov 11 23:31:50 CET 2004
On Thu, Nov 11, 2004 at 11:14:23PM +0100, Frank Barknecht wrote:
> Hallo,
> B. Bogart hat gesagt: // B. Bogart wrote:
>
> > Anyone has a suggestion on how to force my pool data to save in the same dir as
> > the parent patch of the abstraction, rather than the directory where the
> > abstraction resides?
>
> This question comes up very often, actually. In RRADical I use the
> only solution, that in my experience always works: use absolute paths
> like you get them from [open/savepanel]
>
> I am convinced: relative paths are The Wrong Thing To Do In Pd (tm)
> - except for some usecases like namespacing.
>
> (It surely is possible to hack around the fact, that abstractions
ive always just done this, but i guess if you open another patch in the meantime it might be off..
#N canvas 0 0 454 304 12;
#X obj 188 59 tot .;
#X msg 188 38 query global pd_opendir .: list $pd_opendir;
#X obj 188 80 print;
#X connect 0 0 2 0;
#X connect 1 0 0 0;
> don't know their parents when they are written - for example using
> some Python scripting - but IMO it's hacking and thus should be left
> to Yves [excuse the silly Graz reference].)
>
> Ciao
> --
> Frank Barknecht _ ______footils.org__
>
> _______________________________________________
> PD-dev mailing list
> PD-dev at iem.at
> http://iem.at/cgi-bin/mailman/listinfo/pd-dev
More information about the Pd-dev
mailing list