[PD] [PD-announce] Pd-extended 0.43.4 released!)

[Jonathan Wilkes]

----- Original Message -----

> From: Hans-Christoph Steiner <hans at at.or.at>
> To: Ed Kelly <morph_2016 at yahoo.co.uk>
> Cc: Jonathan Wilkes <jancsika at yahoo.com>; "pd-list at iem.at" <pd-list at iem.at>
> Sent: Friday, February 1, 2013 10:48 AM
> Subject: Re: [PD-announce] Pd-extended 0.43.4 released!)
> 
> On 02/01/2013 08:55 AM, Ed Kelly wrote:
>>  OK, so Pd-extended doesn't load any libs by default (except Gem of 
> course).
> 
> There is some confusion there since all of the version/loading messages no
> longer show by default.  The same libraries are all still being loaded by
> default, and the messages are still being posted to the Pd window, but at the
> 'debug' level.
> 
> 
>>  I'd like to suggest a fix for a problem I've encountered, 
> especially when moving patches. 
>> 
>>  Would there be a reverse way of finding out what libs are missing from a 
> patch? Even just to generate a file, it would be a good idea to be able to 
> search the libs and find out what you need to [import] to get a patch made on 
> pre 0.43 Pd-extended to work.

If there isn't already there should be a canvas tag common to
all broken objects. Then a gui-plugin is trivial, something like:

foreach obj $broken_objs {
    pdtk_post "$obj might be [lindex $all_objs [lsearch $all_objs $obj]]\n"
}

... where $all_objs is just a list of all objects available in Pd-extended (well,
ones that have a help patch), prefixed with the lib name.

In fact, you can already do this manually-- just look at the Pd console output
when the patch is loaded, and for each broken object error, copy the name of
the object into the search plugin entry widget.  (And choose "Object help patch"
from the dropdown menu.)

In fact, this will work for any library-- whether or not its a libdir, and whether or
not it's loaded or even compiled-- as long as there is a *-help.pd patch for the
object or objects in the standard search paths of Pd.

-Jonathan