Forums > MaxMSP

Feature request: 'set' message to [select]

February 3, 2011 | 2:10 pm


Is there any chance of adding a ‘set’ message to the [select] object, please?

Kind regards,

February 3, 2011 | 2:51 pm

a set message, unlikely, this would break old patches. But if you have a select object with no argument, you get an extra inlet so you can change the argument dynamically. The request is registered though.

February 3, 2011 | 8:17 pm

hehe, i love this FAQ.

indeed it does accept "select", but only if it has no arguments i.e. it only
works with 2 outlets.

i also found that out not before making an abstraction for that task.

February 3, 2011 | 9:44 pm

Many thanks for your replies folks, all very useful!

Using a [select] object with no arguments will enable me to set up the argument programmatically, which is just what I need to do.

Cheers! :-D

February 4, 2011 | 12:47 am

for dynamic routing of multiple values, I’ve heard about [xroute] but haven’t used it…

Maybe a whole new object instead of [select], like [mselect] for "multiple select". sending a list in would give you that many outlets?

though as usual there are pretty easy workarounds for all this.

February 4, 2011 | 6:45 am

for numbers [if] will also work, and it will work for up of two values
when you dont need the second output for "else".

for more than 2 i´d use several select objects.

February 4, 2011 | 7:32 am

zl, the king of objects, knows a way for multiple values.


– Pasted Max Patch, click to expand. –
Viewing 7 posts - 1 through 7 (of 7 total)