Is it possible to have more than one arguement in the name of a value object?
Working on a Max4Live device that gets and stores all the IDs in a Live Set. Then sets up observers for all the functions.
I’ve got my naming system down and everything abstracted out. So I’ve got subpatches which use say a Device ID and set-up functions to you can call on the device. I’ve got 4 devices set up so one argument 0, one arguement 2, one arguement 3. Send, receive and value objects within the abstractions are then named things like (value —_#1_device_name). This works great at this level.
However, with devices you need to go down a further level as it were and put subpatches in for the parameters. So, what I’d like to have within the above mentioned device subpatch would be 8 copies of a parameter subpatch set with two arguements the first the device number, the second the parameter number. Value objects could then be named something like (value —_#1_#2_parameter_name).
This doesn’t seem to work though. I can’t seem to get a value, send or receive object to load up with more than one arguement in it’s name.
I’m I missing something obvious? Has anyone figured out any work arounds for such things?
some workaround like this might do the trick… that is if I understand the problem correctly. I don’t use M4L myself so I used #0 rather than "—":
----------begin_max5_patcher---------- 375.3ocyTEsaBCBE8Y5WAAydyYJT0V2a6GX+.KFCVXJKsPSAyzY7eekaamSy lZlScOTHb3zKmyob65.DYpYozRvOfeFiPqCPH.xCfZViH47koYbKPinkuYl9 Joa8VN4RG.W1hTvcoyU5YSJkot5ByXC5E1EG0uuehNBFS5EhG27N5E4JclzA m.sA7Ei1o44Rn7OVp3YjszMKb6yWI.lUh6dZTK0ZdtUExZoPHedn95aUuCaP C6E5Q2DD3G5ddYQQorPpEXqzcBoBMxOML5xmJraZpjY3hbo0h6Dh6PwcXGOa XrD+znAW9rgdcxFe.vmIOf0oICAqm.VmxfUzg+j2Y+AdO7lduvVTpztWv2kI lz9ju5IuWN9EjA0sM8iO7MjnyOkhOuPB3PxT58+aKXNO9tIm0rnLs8DZ6dwa smPZcJM2oL5uRJZGRyUBgD1OrAIWIJLUwciHvi+1uimplhOEIwtpRx2HeTME ++Kkp5AwzeojpVrI3C.C7qbq -----------end_max5_patcher-----------