Skip to content

BR_TrackAtMouseCursor() doesn't support the new pinned tracks in TCP #1935

Open

Description

@ovnis82

Activity

  1. changed the title [-]mouse_tr = r.BR_TrackAtMouseCursor() doesn't work anymore with Reaper[/-] [+]BR_TrackAtMouseCursor() doesn't support the new pinned tracks in TCP[/+] on Apr 4, 2025
  2. X-Raym commented on Aug 24, 2025

    @X-Raym
    Contributor

    Confirmed 😮

  3. Moyf commented on Nov 14, 2025

    @Moyf

    Some clues: The height of the pinned tracks appears to add an additional offset to the cursor position.
    #1987 (comment)

  4. acendan commented on Jan 30, 2026

    @acendan

    +1 and easy to repro. Big workflow blocker for some folks using my scripts.

    2026-01-29.09-33-47_hb.mp4
  5. Infrabass commented on Feb 10, 2026

    @Infrabass

    +1, both functions "BR_TrackAtMouseCursor" and "BR_GetMouseCursorContext_Track" are affected by this.

  6. andrummer commented on Apr 11, 2026

    @andrummer

    +1 and easy to repro. Big workflow blocker for some folks using my scripts.

    2026-01-29.09-33-47_hb.mp4

    Just faced an issue, and found out that offset is gone when non pinned tracks are at minimal height :))
    Might be there is a possible workaround on script side?
    used _BR_CONT_PLAY_MOUSE_SOLO_TRACK
    https://github.com/user-attachments/assets/bb78c46e-1c78-4682-99e5-923b98d0b282

  7. X-Raym commented on Jun 23, 2026

    @X-Raym
    Contributor

    The best workarround would simply for the function to now use reaper native API GetThingFromPoint if the function is available (reaper API function check)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions