I’m using a Slider with two thumbs to set a ranged random value for a parameter in a piece of software I’m developing, and am now moving towards integrating this with the AudioProcessorValueTreeState system since it seems to help with some nasty problems.
What is a good way to do this? My assumption is that I should use two attachments targeting the min and max values respectively. I can’t override setValue(), sliderValueChanged() to target slider.get/setMin/MaxValue() in AudioProcessorValueTreeState::SliderAttachment::Pimpl however since Pimpl is private. For now, I’ve cobbled together the methods from Pimpl and AttachedControlBase, and am working with that, but wanted to see if there is something bad about this approach (the two attachments, one for min, one for max) and whether there is a better way to do this, since it’s not terribly maintenance friendly.
If there isn’t, as a feature request, could SliderAttachment take an optional argument that specifies whether it targets min/max/regular value?