Quote:
Originally Posted by juliansader
In the MIDI editor, when trying to use double-click and click-drag mouse actions with mouse modifiers, the single-click mouse action (with the same mouse modifier) is always called and inserted before the double-click or click-drag action is run.
|
This has come up before in different contexts. Unfortunately, there is literally no way for REAPER to know that a single click is just the start of what the user intends as a double-click, so the single click will always be processed first.
(We have even experimented with delaying the single-click processing, but that leads to undesirable behaviors. One place in REAPER where you can see an obvious workaround for this problem is when double-clicking one of multiple selected MIDI items, with "behavior for open items in built-in MIDI editor" set to "open all selected items". The single click will deselect all but one item, but then the double-click restores the previous selection before opening the MIDI editor.)
The only solution is for the user who customizes mouse modifiers to take care that double-click mouse modifiers are not inconsistent with the equivalent single-click modifiers.
MIDI: Double-click and click-drag actions also call single-click action (SOLVED)
Linear Mode
