genekogan

Quick encapsulation question. I want to make an object which takes as an argument a specific number of inlets, e.g. "mypatcher 5" makes an instance of mypatcher with 5 inlets. Kind of like of how pack 5 makes a pack object with 5 inlets. Then inside mypatcher I must be able to iterate through the variable arguments. How can I do this?

Quick encapsulation question.  I want to make an object which takes as an argument a specific number of inlets, e.g. "mypatcher 5" makes an instance of mypatcher with 5 inlets.  Kind of like of how pack 5 makes a pack object with 5 inlets. Then inside mypatcher I must be able to iterate through the variable arguments.  How can I do this?

variable-number-of-patcher-inlets

i think it's the kind of thing uneasy to do in maxMSP. At first sight maybe you should give a look at [patcherargs] in order to more easily handle the number-of-outlets argument but that's maybe not a so good idea ; essentially you need to use the thispatcher scripts with like "script newobject newtextobj outlet" or so... which would be iterated a number of time equal to the number of outlets wanted, you also need a script to connect those outlets, and a calculation for placement :)

In fact the best way I have found to handle this is to figure out the maximum number of [inlet]s you will use and then create these objects from the very start. Give them scripting names with numeric indexes. Then on instantiation your abstraction will need to delete the [inlet]s it doesn't need (thus preserving any connections made in a saved patch). Have a look at the [thispatcher] object helpfile for deleting (and maybe connecting) objects. You will probably need [patcherargs], [sprintf] and [uzi] to automate the process.

variable number of patcher inlets