A library name change is one way to handle that, there are other ways too:
- implement the new search path in Pd so you don't have to rename anything
(best option)
- rename the [pmpd] object
And from the point of view of Pd-extended, a new name would be a new library. Since Pd-extended is already too big to be maintainable, I can't really accept new libraries unless I see that someone has already stepped up and is a responsive, self-sufficient maintainer.
It it now easy to distribute standalone libraries for both vanilla and pd-extended if the library is based on the Library Template and users use the standard install locations:
http://puredata.info/docs/developer/LibraryTemplate http://puredata.info/docs/faq/how-do-i-install-externals-and-help-files
.hc
On 01/09/2013 10:04 AM, Marco Donnarumma wrote:
yep, that works, thanks! Should have tried that....
in any case, I tried modifying the name of the lib folder and the *-meta.pd file to pm4pd, and that works as it should. So yes, Cyrille, renaming might be a good thing to do for the next release.
cheers, M
maybe try: pmpd/pmpd2d? I often have this problem... I think it's because the library has the same name than the object pmpd n
for future pmpd release, would it help if i rename it pm4pd, so that the lib did not have the same name as one object?
cheers c
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list