You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If same ccLane is seen >1 in MidiEditor BR_GetMouseCursorContext() doesn't recognize the 2nd following lane.
Only the first.
Also in the height calculation the 2nd lane of the same CC is missing:
As seen in the GIF, this also affects returned values of functions like BR_GetMouseCursorContext_MIDI().
-- CONSOLE OUTPUT --
function Msg(param)
reaper.ShowConsoleMsg(tostring(param).."\n")
end
function main()
reaper.ClearConsole()
local scale = select(2, reaper.ThemeLayout_GetLayout('tcp', -3))/256
--Msg(scale)
local window, segment, details = reaper.BR_GetMouseCursorContext()
local retval, inlineEditor, noteRow, ccLane, ccLaneVal, ccLaneId = reaper.BR_GetMouseCursorContext_MIDI()
Msg(segment)
Msg(ccLane)
Msg(ccLaneId)
reaper.defer(main)
end
reaper.defer(main)
Sexan already ran into the issue and reported about it when he was developing his PIE script.
All scripts using this function will be affected under certain circumstances about this bug.
I hope this helps to make this very useful functions even more useful.
Best regards, Oliver
The text was updated successfully, but these errors were encountered:
If same ccLane is seen >1 in MidiEditor BR_GetMouseCursorContext() doesn't recognize the 2nd following lane.
Only the first.
Also in the height calculation the 2nd lane of the same CC is missing:
As seen in the GIF, this also affects returned values of functions like BR_GetMouseCursorContext_MIDI().
Sexan already ran into the issue and reported about it when he was developing his PIE script.
All scripts using this function will be affected under certain circumstances about this bug.
I hope this helps to make this very useful functions even more useful.
Best regards, Oliver
The text was updated successfully, but these errors were encountered: