New Patcher argument behavior?


    Mar 02 2011 | 9:11 pm
    For some reason, I am surprised by how patcher arguments work for me right now. Everything works as expected in a 'proper' abstraction that i have saved in max's path. but if i encapsulate something the topmost patcher arguments apply. i remember the difference being that #1 in an encapsulation would be the patcher name but after that arguments were 'normal'
    I am using Max 5.1.8 44740

    • Mar 03 2011 | 4:17 am
      does the radio silence mean it is just me?
    • Mar 03 2011 | 5:16 am
      It just works this way. You can use the patcherargs objects, though.