[PD] declare and abstraction
msp at ucsd.edu
Tue Oct 8 17:20:33 CEST 2013
There's a long-standing bug with putting declares in abstractions (they
affect the way the _parent_ patch searches for patches, not the abstraction
itself.) It's on my dolist to try to restore sanity to the situation somehow
(compatibly) but I won't be able to do that anytime soon.
So, yes, for now put all the declares in the toplevel.
On Tue, Oct 08, 2013 at 05:16:17PM +0200, Cyrille Henry wrote:
> but i really want to be able to work on "patch1" without having to open "patch".
> Le 08/10/2013 16:30, Frank Barknecht a écrit :
> >Hi Cyrille,
> >I struggled with that for a long time myself. Unless something changed in
> >0.44/0.45 the only really reliable solution I found was to *only* use [declare]
> >in a *toplevel* file, and never in any abstraction. So for your layout I would
> >only put a [declare] into "patch.pd" like:
> >In patch.pd:
> > [declare -path .
> > -path dir1 -path dir2
> > -path dir1/abstraction1 -path dir2/abstraction2]
> >Note that the first path that I always set is to the current directory (".") -
> >it's useful to have as well.
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
More information about the Pd-list