#&, #2, ... variables in bpatchers ?


    Feb 13 2008 | 7:57 am
    is there a simple way into having #1, #2, and/or [patcherargs] working in bpatchers ? i have identical modules with pvar/pattr/pattrstorages nested in them which i need to name differently for each module and i dont want to use #0 type of variable names. cheers

    • Feb 13 2008 | 8:17 am
      On Feb 12, 2008, at 11:57 PM, karl-otto von oertzen wrote: > is there a simple way into having #1, #2, and/or [patcherargs] > working in bpatchers ?
      They work fine. Just enter the arguments in the inspector.
      -C
    • Feb 13 2008 | 8:40 am
      karl-otto von oertzen schrieb: > is there a simple way into having #1, #2, and/or [patcherargs] > working in bpatchers ? i have identical modules with > pvar/pattr/pattrstorages nested in them which i need to name > differently for each module and i dont want to use #0 type of > variable names.
      It does work in bpatchers, I am using it all the time... To extract the scripting name of a bpatcher I use a js which comes in handy, as you don't need to open up the inspector to adjust the arguments. Look at the mynamber object in the abhaXions...
      patcherargs doesn't work in poly~ and pfft~. I hope this will be resolved in Max 5...
      Stefan
      -- Stefan Tiedje------------x------- --_____-----------|-------------- --(_|_ ----|-----|-----()------- -- _|_)----|-----()-------------- ----------()--------www.ccmix.com
    • Feb 13 2008 | 9:05 am
      thanks Chris and Stefan , i guess i never really noticed that BIG WHITE RECTANGLE that says "Arguments to patcher" .... sorry for the bandwith ill check your JS Stefan , thanks
      Quote: Stefan Tiedje wrote on Wed, 13 February 2008 09:40 ---------------------------------------------------- > karl-otto von oertzen schrieb: > > is there a simple way into having #1, #2, and/or [patcherargs] > > working in bpatchers ? i have identical modules with > > pvar/pattr/pattrstorages nested in them which i need to name > > differently for each module and i dont want to use #0 type of > > variable names. > > It does work in bpatchers, I am using it all the time... > To extract the scripting name of a bpatcher I use a js which comes in > handy, as you don't need to open up the inspector to adjust the > arguments. Look at the mynamber object in the abhaXions... > > patcherargs doesn't work in poly~ and pfft~. I hope this will be > resolved in Max 5... > > Stefan > > -- > Stefan Tiedje------------x------- > --_____-----------|-------------- > --(_|_ ----|-----|-----()------- > -- _|_)----|-----()-------------- > ----------()--------www.ccmix.com > > > ----------------------------------------------------