Hi Andrew, your OSC-REST comes very handy to interface TouchOSC with RestAPIs to remote control various applications, so I really appreciate your work.
Unfortunately, the lack of a method of passing the parameters and wrapping them with headers in a different format, as you already say in the description, actually limits its usage with TouchOSC because TouchOSC allows to build arguments by concatenating different values (also allowing conversion of different values) but right now OSC-REST manages such concatenation as different parameters, not as a single one.
My question is: it takes too much of your time to also make the /OSC/REST/GET command able to accept a number as 1st parameter and such number to tell how many of the following received parameters to be treated as a single string?
Thank you in advance for your feedback about this request.
Regards,
MD
Hi Andrew, your OSC-REST comes very handy to interface TouchOSC with RestAPIs to remote control various applications, so I really appreciate your work.
Unfortunately, the lack of a method of passing the parameters and wrapping them with headers in a different format, as you already say in the description, actually limits its usage with TouchOSC because TouchOSC allows to build arguments by concatenating different values (also allowing conversion of different values) but right now OSC-REST manages such concatenation as different parameters, not as a single one.
My question is: it takes too much of your time to also make the /OSC/REST/GET command able to accept a number as 1st parameter and such number to tell how many of the following received parameters to be treated as a single string?
Thank you in advance for your feedback about this request.
Regards,
MD