[PD] The parent patch file name... state saving

[david golightly]

Hello all, my 2 cents:

What I've done is coordinate the initialization of multiple instances of the 
same abstraction in a parent patch with an argument, as $1:

[loadbang]
|
[$1]
|
[sel 0 1 2 etc]
|           |
[; init a(  |
           [; init b(

etc., so that different states can be automatically loaded based on the 
initialization arguments assigned to it in the parent patch.  This works 
fine for me.  Does that make sense?

David



>From: Frank Barknecht <fbar at footils.org>
>To: pd-list at iem.at
>Subject: Re: [PD] The parent patch file name... state saving
>Date: Tue, 6 Sep 2005 17:37:46 +0200
>
>Hallo,
>Frank Barknecht hat gesagt: // Frank Barknecht wrote:
>
> > Hallo,
> > Thomas O Fredericks hat gesagt: // Thomas O Fredericks wrote:
> >
> > > Getdir only outputs the directory in witch the parent patch is and not
> > > the parent patch name!
> >
> > But then:
> >
> >   [getdir]
> >   |
> >   [makefilename %s/PARENT_NAME.pd]
> >
> > will work, as you know the PARENT_NAME anyways.
>
>Ah, sorry, I'm talking nonsense again: "getdir" gets the name of the
>*parent*, right? (I don't use it). Well, then of course the filename
>indeed is unknown and would need to be passed as argument then. Or
>maybe one could change getdir.c to also send out the parent's filename
>
>Ciao
>--
>  Frank Barknecht                 _ ______footils.org_ __goto10.org__
>
>_______________________________________________
>PD-list at iem.at mailing list
>UNSUBSCRIBE and account-management -> 
>http://lists.puredata.info/listinfo/pd-list