Last question - what about persistent arrays in abstractions? Any advice about that? Some of my GOPs are table/array based, often for drawable control data.. I don't think I saw anything about this yet. I am willing to give a shot at developing something for it if it is not included yet.

On 9/16/07, Frank Barknecht <fbar@footils.org> wrote:

Hallo,
Michal Seta hat gesagt: // Michal Seta wrote:

> Sorry, I am not Frank but I think I know the answer to this issue:
>
> 1.  Open an existing rrad abstraction
> 2.  Replace GUI and non-rrad guts with your own.  (leave [pd memento]
> and boxes connected to it intact)
> 3.  Set up appropriate send/receive in GUIs and whatnot.
> 4.  Open [pd memento], find the communs sends and replace them with your own.
> 5. enjo.

Yep, that's basically it. The basic rules are this:

* Put an object [originator $1 $0] into your abstraction.

* connect the leftmost inlets and outlets of that originator to the
  leftmost inlets and outlets of your abstraction. (That's just a
  convention, though.)

* For everthing you want to save, create a [commun /NAME $0] object
  and cross-connect its inlets and outlets to the thing you want to
  save, either a $0-local send/receive or directly. Replace "/NAME"
  with something useful.

  By cross-connect I mean, that you should connect the outlets of an
  object whose state you want to save to the inlet of the commun and
  the inlets to the outlets of commun.

Ciao
--
Frank Barknecht                 _ ______footils.org_ __goto10.org__

_______________________________________________
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list