[PD] Dynamic search paths and [declare] behavior in Pd.0.47

[Miller Puckette]

The trouble with that is that the old behavior depended on what order you created
objects and saved/restored patches in - in other words, it was defective by design.
I know it was possible to work around that, but I can't see any way to make it do
the buggey thing it did and not be buggy.

cheers
M

On Sun, May 08, 2016 at 03:25:01AM +0000, Jonathan Wilkes via Pd-list wrote:
> > But the old behavior was seriously broken and I don't see any good way to provide it without causing trouble and confusion.
> Deprecate the old [declare] and name the new [declare] something else.
> 
> -Jonathan
> 
> 
> 
>     On Saturday, May 7, 2016 8:40 PM, Miller Puckette <msp at ucsd.edu> wrote:
>  
> 
>  I don't regard this as a patch-level incompatibility (I believe you can run all
> the patches -- only now you'll have to add 6 directories to Pd's search path).
> But it's a serious inconvenience for sure.  But the old behavior was seriously
> broken and I don't see any good way to provide it without causing trouble
> and confusion.  I'm open to ideas...
> 
> Miller
> 
> On Sun, May 08, 2016 at 12:09:04AM +0000, Jonathan Wilkes via Pd-list wrote:
> > Hi Jerome,If you're saying that your patches used to work and they now break, 
> > do file a bug about it.  Others on the list have mentioned using 
> > [declare] for this purpose-- I never have but it's a reasonable use case.
> > 
> > -Jonathan
> > 
> >  
> > 
> >    On Saturday, May 7, 2016 7:30 PM, Jérôme Abel <abel.jerome at free.fr> wrote:
> >  
> > 
> >  Hi list,
> > 
> > With the new [declare] behavior, I am a little confused (Pd.0.47). I've 
> > read that putting [declare] in abstractions was not the "right" way, but 
> > that what I've done. Shame.
> > 
> > In La Malinette (malinette.info), it is very useful to have an 
> > abstraction named [include] which contains all relatives paths of all 
> > abstractions folders. The goal is to be user friendly and not ask people 
> > to add 6 paths in preferences ...  And if I want to change a path, to 
> > add a common feature for all patches, I have just to change it once, all 
> > patches that have this abstraction are affected. And I want to add paths 
> > to my patchs I have just to remember the name of [include] to add this 
> > object and paths. These are benefits of having abstractions, like 
> > object-oriented programming.
> > 
> > How can avoid to copy/paste 100 times a subpatch which contains 
> > [declare] and all paths, in all my files ? Or may be there is a way to 
> > add dynamically paths on all patches or current patches ? I can't see 
> > [import] in Deken, may be it could be the right way to add this kind of 
> > feature ? Is it downloable ?
> > 
> > Thanks,
> > 
> > Jerome
> > 
> > _______________________________________________
> > Pd-list at lists.iem.at mailing list
> > UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
> > 
> > 
> >  
> 
> > _______________________________________________
> > Pd-list at lists.iem.at mailing list
> > UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
> 
> 
> 
>   

> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list