The values of the params in the gen~ patcher may not be effective names for a useable control interface.
In order to improve the building of custom UIs on Daisy hardware I propose the ability to add a string at the end of the param name that signifies what shall be displayed instead of the values that are used. I think this particularly makes sense with int or bool parameters that are used for switching modes/settings in gen~ . Since we can only do it in the param name itself your idea from slack sounds good:
I case you end up implementing this it would be perfect, if the param name that gets displayed ignored those value settings (as well as the int/bool setting) to clean up the interface.
I'm punting on this right now as there may be bigger changes scheduled for the OLED UI, now that there's a more generalized set of UI features being developed in libdaisy
The values of the params in the gen~ patcher may not be effective names for a useable control interface. In order to improve the building of custom UIs on Daisy hardware I propose the ability to add a string at the end of the param name that signifies what shall be displayed instead of the values that are used. I think this particularly makes sense with int or bool parameters that are used for switching modes/settings in gen~ . Since we can only do it in the param name itself your idea from slack sounds good:
[param knob1_mode_stereo|pingpong|ms @min 0 @max 2]
I case you end up implementing this it would be perfect, if the param name that gets displayed ignored those value settings (as well as the int/bool setting) to clean up the interface.