Over 9 replaceable pound arguments...

    Jan 30 2010 | 9:04 pm
    Hey guys.
    Upon going into more than 9 # arguments in one abstraction, max starts labeling the arguments differently in instances of the abstraction. Rather than continuing 10, 11, 12 etc, you get "00", "01", "02" etc.
    Is there simply a maximum of nine arguments per encapsulated abstraction, or does anyone know a way round this?
    Thank you.

    • Jan 30 2010 | 9:18 pm
      Have a look at [patcherargs].
    • Jan 30 2010 | 9:48 pm
      I looked at arguments for patcher and couldn't see any to help my problem. I am presuming that is what [patcherargs] relates to, apologies if not, I just haven't come across that format.
      Thank you.
    • Jan 30 2010 | 9:58 pm
      The [patcherargs] object will report the arguments of the containing patcher, then you can [unpack] or [zl slice] or [zl nths] them and send them where you want. Much more flexible than the #1 style arguments.
    • Jan 30 2010 | 10:05 pm
      Oh I see, square brackets indicate an object, apologies for being slow haha!
      I will do some learning, thanks very much!
    • Jan 30 2010 | 10:49 pm
      I should have made it clear from the start. I personally use [square brackets] to denote an object and "quotes" when referring to a message. Other people use different ways, objects sometimes appear like this too.
    • Jan 30 2010 | 11:30 pm
      I've investigated those objects and they've allowed me to do exactly what I wanted so that you Luke! I'm often surprised at the ease with which some things in Max just pass me by for so long!