musescore / musescore/MuseScore

Mouse note entry: imaginary position shifts with bar size

Open
#25,937 0 comments 0 reactions 2 assignees View on GitHub

@bkunda is already working on this.

Since Jan 9, 2025.

feature request P3 UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

outtake from #25936.mp4

On note entry with the mouse, the location of the pointer is gaslit. After entering beat 1 (similar to writing text, or on paper[^whoknows]), the hand is used to shifting a bit right (to the previously imagined beat 2 position). The new position is surprisingly beat 3 — the mouse got lost! Had to readjust by moving to left.

[^whoknows]: Who knows, maybe persons growing up with only screens expect the change? Does it not break their flow? Do we even have people who don't know how to write with a pen(cil)?

image

While driving, one divides an unmarked road in to two, and by default keeps to the (cough) right side. When looking at a bar (step 1, 2), it can be divided into 4 imaginary beats. After some note entry, the engraving renderer determines, that you need more space, and makes the bar bigger. This disorientates the mouse and eyes (with keyboard entry as well).

Prior art

On closing tabs, Firefox keeps the tabs size, and reconciles after the mouse/attention is not on the tab bar. 2024-12-29 06-25-42.mp4

Supporting files, videos and screenshots

above

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

4.4.4

Regression

No.

Operating system

Arch

Additional context

No response

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

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.