Ludde wrote:
Dear list members,
I think there is a problem with the load path of patches in PD. I have a situation where there is patches in a library and in the startup directory. Now I like to override some patch in the library by adding a modified version of it in the startup directory. I think this should be a rather good idea but PD does not handle the situation as I would like. If you try to override a patch that is includen in another patch in the library then PD will open the one from the library and not from the startup directory as I would like. How can you tell PD to first look in the startup directory? I have tried to solve the problem without success by using the -path in the starup command. How can this problem be solve? What do others think about the search order?
i have to admit, that i do not really clearly understand what you mean: if you have an abstraction (like "abstrakt.pd") in one of your search-paths (pe path/pd/extra) and you use it in your patch, it will be loaded (aha!). if you create a (better) abstraction "abstrakt.pd" in the directory where your patch is saved (say ~home/pd/patches/), this one will be used... so where is the problem ?
if you want to change pd's behaviour, that libraries are preferred to patches (as it is now) i agree with krzysztof, that this is rather a bad idea...
anyhow, you can force a patch to be loaded (even if an external of the same name exists), by giving (sufficient parts of) its path: pe "./abs" will load an abstraction abs.pd in the current directory, although the function "abs" is built into pd
mfg.c.sdaf IOhannes
Best regards, Peter Lunden