The way picking works seems to be really inconsistent; I suspect this has something to do with you're checking for IsPickingDataValid and didMove. The result is that certain data types like pulse and momentary can't be triggered at all from multitouch, and the interface often gets stuck thinking you're still interacting with the left half of the ui when you're trying to work with individial parameters on the right. Parameters still need to be double clicked to engage with mtouch, which is unintuitive, and doesn't work very consistently so it feels clunky. I suspect this is because unlike using a touchscreen on regular sliders, this UI needs to know what is being hovered over before it engages, and that extra layer of abstraction is borking something
EnviralDesign
commented
3 years ago
The way picking works seems to be really inconsistent; I suspect this has something to do with you're checking for IsPickingDataValid and didMove. The result is that certain data types like pulse and momentary can't be triggered at all from multitouch, and the interface often gets stuck thinking you're still interacting with the left half of the ui when you're trying to work with individial parameters on the right. Parameters still need to be double clicked to engage with mtouch, which is unintuitive, and doesn't work very consistently so it feels clunky. I suspect this is because unlike using a touchscreen on regular sliders, this UI needs to know what is being hovered over before it engages, and that extra layer of abstraction is borking something