take care to the comma in a list: it divides this list in 2 parts. Not so easy to route

[t b b b b] [list 1 2 3] [list 1 2 3] [list 1 2 3] [list 1 2 3]

Thanks Mizu, that works perfectly.

I didn't realise that commas separate lists, seems a bit strange when commas also separate messages (like in ramps), doesn't this create problems when using lists and ramps together? Or am I looking at it the wrong way?

Roman I'm afraid I don't understand what your answer what was suggesting...

Roman is right to clearly think how the commands need to be organised. Visually i prefer use 2 messages, and triggers, easyer to work a patch. Complex messages separated by commas makes the same job, but for me, less readable and editable. Useful i.e to send some static data to initiate a patch. Go to thispacher help : the syntax of the scripting commands use messages and commas

hth zzz

"seems a bit strange when commas also separate messages"

a list is, last but not least, also only a form of message. :)

whether you use [list], [message], [zl reg] or [coll] is a matter of taste.

i like list/pak best because it allows to have dynamic list elements, too, and unlike messageboxes you can see the type of those variables and not be confused by their numbering:

messagebox: "this is fixed but number $1 and $2 are not"

[list this is fixed but number 0. and donald are not ]

a special case is also when your list include symbols containing a comma character.

[list this is fun, this is not] will not work in a messagebox.

Interesting how "list" works, is considered as reserved word in the connections of Max: the object "list" exists and refers to the pack.maxhelp. In messages, i've had some historical perplexities between different OS and Max versions. The 1st place where older patches needed adaptations.

i think list is the original name before it was renamed to pack one day. and i am glad that it is still supprted to call it like that, because it somehow makes sense. :)

Thanks for the clarifications guys. In my short time with Max I've noticed that there are many different ways of doing the exact same thing, and your examples and explanations are really useful in helping understand the program better, so thanks again!