A bit of a noob question here… I recently installed list-abs from deken on a vanilla PD 50-2 on macOS Catalina. My patch wasn’t able to find the abstractions until I explicitly added the path ~/Documents/Pd/externals/list-abs to the Paths preferences. Is that to be expected?
Peter
If I understand the issue correctly, this is to be expected. To be able to load abstractions or one-binary-per-object externals you have the choice of a) adding the path to it to the paths preferences of your Pd installation globally b) declare the path to it in the patch you are using it in with [declare -path list-abs]. It assumes that the root folder for all your externals (~/Documents/Pd/externals/) is defined in the global paths preferences and will append the list-abs folder to that and search for the object or abstraction in there.
Option b) is the newer possibility and has the advantages that you don't have to load all the possible externals at startup and that your patch becomes more portable.
m.
On 01.06.20 21:44, Peter Nyboer wrote:
A bit of a noob question here… I recently installed list-abs from deken on a vanilla PD 50-2 on macOS Catalina. My patch wasn’t able to find the abstractions until I explicitly added the path ~/Documents/Pd/externals/list-abs to the Paths preferences. Is that to be expected?
Peter
On 6/1/20 9:44 PM, Peter Nyboer wrote:
A bit of a noob question here… I recently installed list-abs from deken on a vanilla PD 50-2 on macOS Catalina. My patch wasn’t able to find the abstractions until I explicitly added the path ~/Documents/Pd/externals/list-abs to the Paths preferences. Is that to be expected?
depends.
it is certainly expected that you cannot just start creating [list-map] objects without further ado.
you must "load" the library first.
the modern way to do that is to declare that you want to use this library in each patch that uses this library. (this is similar to a plethora of other programming languages, e.g. Python, where you have to "import" a library before you can use it in a .py file)
you can declare this dependency by putting a [declare -path list-abs] in your patch.
(you can also put that path in the preferences as you did; but this hides the fact that a patch depends on an external library, and makes it harder to share/port to another system).
gsfdmr IOhannes
Em seg., 1 de jun. de 2020 às 16:56, Peter Nyboer p@nbor.us escreveu:
A bit of a noob question here…
well, this can help you :) http://msp.ucsd.edu/Pd_documentation/x4.htm
-
Alexandre Torres Porres -
IOhannes m zmölnig -
Max -
Peter Nyboer