Hello, One possibility : A patch is a text file. In this file each object is represented with a line beginning with : #X obj ... For example, a [drip] at position (179,93) is : #X obj 179 93 drip;
So it could be doable, with the [text] object, to analize your patch and return each object. Then you can get a list of externals. ++ Jack Le 28/02/2016 13:26, Alessio Degani via Pd-list a écrit : > On 27/02/2016 16:35, IOhannes m zmölnig wrote: >> On 02/27/2016 12:05 PM, Alessio Degani via Pd-list wrote: >>> Is there a simple way to chek if a pd patch is made only using vanilla >>> object? > > Hi IOhannes, > >> as in: install Pd-vanilla, start it with "-noprefs -verbose" and load >> the patch? > Thank you for the answer. > That works. But how about a more direct "this patch uses the following > libs/extern: ...". > Do you think that is feasible? > Maybe in a future release of pd > > Cheers > >> then see if any object couldn't create. >> then check the Pd-console to see where it found the objects that it >> could create, and check whether any of those are outside your patch path. >> >> >> >> gfmsarI >> IOhannes >> >> >> >> _______________________________________________ >> [email protected] mailing list >> UNSUBSCRIBE and account-management -> >> http://lists.puredata.info/listinfo/pd-list > > > -- > a. > > > > _______________________________________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
