Percussion shadow note does not follow cursor

Open
#26,557 5 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Assessment

This issue has not been assessed yet.

Description

os: linux UI
Issue type

UI bug (incorrect info or interface appearance)

Description with steps to reproduce
  1. Add a drum kit instrument
  2. Enter note input mode
  3. Start clicking notes into the staff

Result: the shadow note stays locked into the same segment where note input started, rather than following the note input cursor.

Supporting files, videos and screenshots

Image

What is the latest version of MuseScore Studio where this issue is present?

OS: Debian GNU/Linux 12 (bookworm), Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.0-250480306, revision: github-musescore-musescore-dec1cc5

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

Debian 12

Additional context

I have also noticed in some cases, the shadow note will jump to a new location, but it seems kind of random as to when it happens and where it jumps to. The one thing I see fairly consistently is that if I switch to another window and back, the shadow note does start following my mouse, until I click in a note, and then it becomes locked again.

FWIW, I also do not see the popups that I see in other screen recordings from https://github.com/musescore/MuseScore/pull/26000#issuecomment-2663381611. I'm not sure if this is meant to be enabled already or if I'm supposed to do something to enable them, or if this is somehow related to why my shadow note isn't working.

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from musescore/MuseScore

All issues in musescore/MuseScore

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.