this might help to clear up the confusion due to the different nature of $1, $2, etc in objects and message boxes...

the general ascii way to denote an object is inside square brackets [objectname]

message boxes are displayed a number of ways, but the most common seems to be a square bracket followed by backwards round bracket... ie [message(

************************
$1, $2 etc in OBJECTS
************************

here is a normal [pack] object with 3 floats:

[pack 10 50 100]

if we use this inside of an abstraction, instead of 10 50 100, we might want to use $1 $2 $3, so that every instance of the abstraction can be initiated with different values.

for example, we might make an abstraction called 'multi-tap.pd', and inside the abstraction there is [pack $1 $2 $3].

if we initiate this abstraction in another patch, we can use "creation arguements" to fill the $1 $2 $3 spaces.

eg.. [multi-tap 7 40 300]

inside this abstraction, for any OBJECT with $1 in it, the $1 will be substituted with '7'...$2 will be substituted with '40' and $3 will be substituted with '300'

so, [symbol $1-tigers] in this case will output 'symbol 7-tigers' when banged.

the exception to this case would be something like [symbol sample-$1.wav]. that won't work, because the $1 sign must come first.

********************************
$1, $2 etc in MESSAGE BOXES
********************************

message boxes can also use $1, $2 ..etc (but never $0) however, the function is very different.

dollar signs in message boxes will just pass on the information sent to their input. here are some examples:

this patch will print out 10 50 400:

[bang(
|
[pack 10 50 400]
|
[$1 $2 $3 (
|
[print]

this patch will only print out 50:

[bang(
|
[pack 10 50 400]
|
[$2 (
|
[print]

we can also add stuff after a dollar sign, like this:

[numberbox]
|
[symbol $1-array(
|
[print]

be careful though, as the following won't work. the $ must come first:

[numberbox]
|
[symbol array-$1(
|
[print]

***********************************************************************
for more information, right click on a message box for its help file.

(sorry, i don't think this explanation is very good. i will think about how to make it clearer when i add it to the wiki)

No, it's really a great help and becoming clearer all the time - thanks for putting the time in. It's highly appreciated.

no problem.

we're going to put up a 'pdpedia' wiki soon, so it's good to start doing drafts here on the forum.

Ah, Mr Hardoff.

Thank you for explaining this.

It all makes so much more sense now.

*goes off with a new trick to put into a patch one day*

Another good one Hardoff. May I suggest some ways it might be clarified?

every instance of the abstraction can be initiated with s/different values/ the values passed to the abstraction/

"the exception to this case would be something like [symbol sample-$1.wav]. that won't work, because the $1 sign must come first."

I think this changed past 0.40

dollar signs in message boxes will s/just pass on the information sent to their input/ substitute the Nth member of a list in $N

Great work , will be good to add in the pdwiki.

i haven't got 0.40 yet. but if that has been changed that's awesome. the wiki will be good for this type of thing, as someone like me can add a basic page, and then someone can come and edit or clarify it. seems like the best way to make a good pd info resource.