I would like to see the [route] internal object to be
"settable", maybe similar to the way, [select] is
settable if no creation argument to [select] was provided.
There is the [nroute] external in maxlib, which does
this and more, but having a simplified version as
builtin would be really great and it would make
"select" and "route" behave more consistent.
Anonymous
Logged In: YES
user_id=1541432
Originator: NO
I posted a "troute" abstraction to the list that uses namecanvas black magic to achieve this (it takes a list to change its arguments).
I perhaps ruined its simplicity by trying to have the outlets change dynamically as well when the number of arguments changes (for no reason at all!), but it is quite reliable for a fixed-number-of-arguments.