[PD] Best way to make file paths relative to the parent patch ?

Jérôme Abel abel.jerome at free.fr
Sat Oct 7 16:33:39 CEST 2017


To explain myself, i have to describe a practical example 
(http://reso-nance.org/public/pd-malinette/test-paths.png) :
- you write an [audio-sampler] abstraction in "abs" directory, which 
load soundfiles
- you write a "main.pd" patch where you put this abstraction in the 
project directory
- you want to load the "data/snare.wav" sound file with a message 
connected to the abstraction

Result : the context of the abstraction is in "abs" directory, so it 
can't find "data/snare.wav" (there is no "abs/data/snare.wav" file), 
instead we have to write "../data/snare.wav" relative to the abstraction 
and not the parent patch.

A common solution to deal with that is to add [ggee/getdir 1] inside the 
abstraction, to get the absolute path of the file starting from the 
upper level (parent patch). But if the abstraction is inside another 
abstraction, it has to be [ggee/getdir 2] and so on ...  But how find 
the right depths of the abstraction ? The abstraction doesn't know his 
context of use.

I think I will put a [ggee/getdir 10] or greater to be sure to get the 
parent patch level, but maybe someone has another solution, a vanilla 
solution ?

Related PR :

  * https://github.com/pure-data/pure-data/pull/150


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20171007/5663cf38/attachment.html>

More information about the Pd-list mailing list