BR_GetMouseCursorContext broken

[saxmand]

I'm trying to use BR_GetMouseCursorContext to get details on the envelope lanes without luck. I believe it's broken.
The only thing I get is "envelope segment" when it's in an automation item.
I've checked on MacOS and @nofishonfriday checked on Windows.
I've tried with the latest version of SWS and this simple code below.

Testing script:

function msg(m)
  return reaper.ShowConsoleMsg(tostring(m) .. "\n")
end

lastDetailsOut = -1

function GetMouseCursorDetails()

  windowOut, segmentOut, detailsOut = reaper.BR_GetMouseCursorContext()
  
  if lastDetailsOut ~= detailsOut then
    msg("detailsOut: " .. detailsOut)
  end
  
  lastDetailsOut = detailsOut
  
  reaper.defer(GetMouseCursorDetails)
end

GetMouseCursorDetails()

The issue was also tracked earlier here:
#1735

[cfillion]

Thanks, fixing! As a workaround you can disable the lane option "Project default behavior outside of automation items".

Also there will be builds in the pull request linked below in about an hour.

[saxmand]

That's awesome. I've not been able to find the option you mentioned. Will check the build tomorrow.

[cfillion]

It's in the envelope lane's context menu:

[saxmand]

Nice.

So I checked the build. It's close to working.

• It seems to overshoot the position of points and segments a bit, so when I'm a little below a point or segment it already thinks I'm at them, and when I go to the "top" of a point, it sees it as empty.
• it does not catch points inside Automation Items

I wonder if the overshoot has to do with padding. Not sure if it's using the underlying reaper.GetEnvelopeInfo_Value, cause then maybe it should use I_TCPH_USED instead of I_TCPH?

I included a video just as it might be easier to see than a gif, cause you can start and stop:

BR_GetMouseCursorContext.behavior2.mp4

[nofishonfriday]

It seems to overshoot the position of points and segments a bit, so when I'm a little below a point or segment it already thinks I'm at them, and when I go to the "top" of a point, it sees it as empty.

Yes, the detection offset appeared when automation items were introduced, because of their bottom 'strip', I think the whole envelope got shifted upwards then.

[saxmand]

Appreciate it. Makes sense.