Copying String arguments in OSC

Have a look to the discussion https://community.etcconnect.com/etclabs/f/lighthack/28539/can-t-install-box_1_src---please-help
Maybe my code I published helps you. 

So from what I'm seeing, this uses an index and struct to assign a string corresponding to a parameter to the encoder, but it isn't using anything from the console to determine which string to assign. I want an argument of the OSC message to determine what to parameter is assigned to the encoder.

Planning to look into using pattern matching from the OSC lib next.

The first item of the struct is the parameter name from the console, the second is the name you wont see on display which is optional. The parameter name are fixed, maybe you want do it dynamicly?

Which micro controller you use? Teensy? I'm working also on a project with 3 encoders with dynamic parameters.

Yes, the plan is to make the parameters dynamic. I'm thinking I'll use Match to compare your struct parameter names with /eos/out/active/wheel/ to determine what encoders are active.

Currently I'm using an UNO, just because it was what I have available for prototyping; once I've got it working, I plan to move to a Feather M0. I've got a couple of teensy based projects and it is a GREAT board, but I want to see what the Feather can do.

/eos/out/active/wheel will get you some part of the way but some of the parameter names don't match to their parameters if you want to control with the parameter rather than the /wheel.  Mixing of the two formats doesn't currently work for anything that would have a space in the name and many of the more complex named parameters.  If you use the/wheel you can get what category that each wheel is in but you are locked to using the wheel number to control the parameter.  If you use the parameter name you can't get the dynamic selected parameters.  It's a bit of a conundrum. You have to choose which part of the puzzle you want and stick with it.

/eos/out/active/wheel will get you some part of the way but some of the parameter names don't match to their parameters if you want to control with the parameter rather than the /wheel.  Mixing of the two formats doesn't currently work for anything that would have a space in the name and many of the more complex named parameters.  If you use the/wheel you can get what category that each wheel is in but you are locked to using the wheel number to control the parameter.  If you use the parameter name you can't get the dynamic selected parameters.  It's a bit of a conundrum. You have to choose which part of the puzzle you want and stick with it.

Helpful infos, thank you. I will give dynamic parameters a try, I know it will a hard fight. I think if a parameter name send with /eos/out/active/wheel, you must replace the space with an underline, hope this will work.