[PD-dev] saving preset pools in the parent path, rather than the abstraction path?

[Hans-Christoph Steiner]

On Nov 11, 2004, at 5:14 PM, 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
> 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].)

Absolute paths are a real hardship when it comes to making portable,  
cross-platform patches.  Anyone know what needs to be done so that we  
can use relative paths everywhere in Pd?

.hc

________________________________________________________________________ 
____

"Information wants to be free."
                              -Stewart Brand