PURE DATA forum~

The initialized values are saved in the abstraction itself, and will only be saved when you save the abstraction, not the parent patch. So if you have several of these in the parent, you'll need send the values somewhere in the parent, like in an array, and save them in the parent patch.

don't feel dumb, it's actually not a simple task - well, not nearly as simple as it should be. 

i have attached a little example of what maelstorm means about sending the data outside of your abstractions to be saved in the parent patch.  There are a million different ways to do this though, this is just one of them.

without even looking, i can guess that you're using dollar signs in messages?

dollar signs act differently in messages than they do in objects (of which abstractions are a part).

this issue really needs a new tutorial.  i'd do it now, but i have been out and had a couple of ales.

Thanks mod, the [pack] object did it, i tried [read -resize $1 $2-soundfiler( before without [pack] and that didn't work. [pack] and [unpack], [list], [route].... ok, i really have to go into it now, they seem to be absolutely essential. Thnaks for helping me out here, I'm making progress and hopefully others who read this will go ahead as well

Yes, a tutorial would be a good idea, i think hardoff made a very good one for dollar signs in object boxes and that helped me a lot, but the slightly different meanings of dollar signs in objects and messages can be very confusing. It's not too hard to get the idea, but using it within your own abstractions is another thing when you never did this before. Studying patches in quest of specific information is often quite painful and even more confusing, but, on the other hand, challenging. Ok, but using dollar signs in abstractions is such an essential part of Pd, some more examples could really speed up learning Pd, on the web there are not too many illustrations regarding this subject (or maybe i didn't find them) and the manuals that come with Pd are also a little bit shy sometimes....

Bla bla... Have a good time

Last edited by wk (2011-11-11 21:29:00)

If those abstractions are using $0 in all of their [send ], [receive ], [send~], [receive~], etc. objects, then there shouldn't be any cross-talk. See Help Browser --> PureData --> 2.control.examples --> 13.locality.pd

Subpatches are a different story. They don't get a unique $0 assigned to them (they just use the same one as the parent patch), so you have to be more explicit with the names. If the subpatches are all copies of each other, it could be easier to just make them into abstractions and use $0.

mod wrote:

i have attached a little example of what maelstorm means about sending the data outside of your abstractions...

Thank you for the state-saving example, Mod. I am a beginner so please excuse this simple question: Why do your gui-examples know, that their names are test and test-2? I can´t find the source of the naming, neither within the subpatch gui-example nor the master patch state-saving.

Thank you for any insights

It's also possible to send data via a [set $1( etc. message into an empty message and simply give it a loadbang, which i found is very handy if you don't need to save very long lists, only a few toggles or sliders or whatever