ok. say you want to create a very simple sample player. you'd do something like this.

[0] <-- gui bang object #1

http://www.hispasonic.com/blogs/03-abstracciones-pd-uso-signo/2770

Thank you very much again!

within main abstraction [mainAb]
some data named $0var send it like this

initialize sub abstractions
pass names X_1 and X_2 in so you can send and receive data to these abstractions individually
[abX X_1 $0] [abX X_2 $0]

within sub abstraction abX initialized with X_1
$1 = X_1
$2 = mainAb's $0

for all instances of abX
to receive from main's
[r $2var]

to to send and receive locally and have mainAb access
within abX
within mainAb [r $0X_1varZ] and [r $0X_2varZ]

a way to get global data to sub abstractions of abX
within abX initialize [abY $2var]
within abY $1var = mainAb $0var

This information is useful say if you have multiple voices and want to have them share the same control

so say $0var is a send on a filter frequency slider
when you move the slider all instances of abX receive the new filter frequency

when you want information to or from a specific instance of abX say like you want to plot each of the voices outputs on a scope
use [s~ $2$1varZ] in abX
then in main [r~ $0X_1varZ] and [r $0X_2varZ] then you can write those to a table so you can see which voice is sounding

thanks for the nice example which I bumped into whilst looking around the forum. It's also interesting as I'd just read elsewhere on the forum a whole blurb on not using abstractions! If I find the discussion again I'll post the link here.

In the meanwhile .....

It would be nice (to finish your explanation) that you explain 'why' $1 $2 as, "$1, $2 ..etc is a bit easier to understand". Maybe for the non-beginner, but you could explain anyway, this way your tutorial would be 100% clear.

There also a very nice, and clear, explanation for anybody interested in the Floss Manual on PD producing a patch using $0 that spits out the random value each time you open the patch. It's in Chapter 38.Dollar Sign Arguments for anyone interested.

(in many situations, i'm not a big fan of abstractions, and i'd really much prefer if subpatches could use $0 locality like abstractions do.)

if you want to go ahead and edit/extend my explanation, then please do! just post the missing bits here, and i'll attach them to the original post.

You don't need to add on anything, you already wrote two excellent (and very clear) explanations here expanding on the why $0 and why then $1, $2 etc. :

http://puredata.hurleur.com/sujet-6417-dollar-signs-objects-messages
http://puredata.hurleur.com/sujet-6314-abstractions-problem

That's how I ended up here (on this thread).

I'll look out the other post as I can't see it at the moment.

I'm not Maelstorm, I just wish i was

Nice post though, thanks.

is that the issue?

if not, then post your patch with some annotation of the issue. and it should be easy to figure out

yes, i think this is a bug. i have no idea why the table appears on your parent patch. hmmm.... it does not behave that way here. i wonder why it does that for you?

anyway, your patch uses a GUI array in the sample-playa abstraction, so how about if you change that to a non-GUI table?

http://www.pdpatchrepo.info/hurleur/sample-playa.pd