BrainModular

I edit a lot of values by typing rather than moving sliders. Especially x and y and height and width values for controls. And I still cannot reliably get a double-click to work the first time on a control. The reason is that usine moves your mouse to the 'hot spot' of the control after the first click.

Could there be a 100 ms delay before usine moves your mouse to wait for the second click? Or could it respond to the second click as a double-click even though it is in a different position the second time??

I even wonder about an option (even globally) to have control values just move to where you click them. especially in controls like the xy module. In the color picker I still always want the cursor to just go to where my mouse is, not have to grab it (tiny and hard to get) and move it over there. In that particular situation, I can see no advantage to requiring me to get the cursor first. In the case of a volume slider, I can see where you might not want that behaviour, as you could get sudden volume changes.... but in that situation, I could put a lag processor in to compensate for that, if it became a problem.

Certainly it would be a useful option for patching faders, even if it didn't affect the module parameter faders (although that's where it bothers me the most

cheers,
=e

unfortunately not so easy because double click event is not generated usine but by the system.
1) for faders and knobs: but it's a good suggestion I'll try to implement it in HH3
2) for xy modules, actually impossible with the mouse, already implemented with touch screen
3) color picker, not a big pb?