I added these 3 setters, because I'm currently working on an external that exposes as parameter to Ableton Live via the getvalueof/setvalueof interface. To set attributes on this exposed parameter, i have to edit attributes on the object using
max::object_attr_setlong, max::object_attr_setfloat and max::object_attr_setvalueof
so I wrapped those in the same place where object_attr_setchar and object_attr_setsym are wrapped. I'm not sure if there's a better way to overload the existing set functions for a more consistent call style, but when I tried just overloading them everything became ambigous obviously.
Here's a simplified snippet from my code where I use these new functions on a min::box that exposes the getvalueof/setvalueof interface:
I added these 3 setters, because I'm currently working on an external that exposes as parameter to Ableton Live via the getvalueof/setvalueof interface. To set attributes on this exposed parameter, i have to edit attributes on the object using
max::object_attr_setlong, max::object_attr_setfloat and max::object_attr_setvalueof
so I wrapped those in the same place where object_attr_setchar and object_attr_setsym are wrapped. I'm not sure if there's a better way to overload the existing set functions for a more consistent call style, but when I tried just overloading them everything became ambigous obviously.
Here's a simplified snippet from my code where I use these new functions on a min::box that exposes the getvalueof/setvalueof interface: