musescore / musescore/MuseScore

Pedaling Marks Are Incorrectly Placed

Open
#25,927 1 comment 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

engraving P2 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
  1. Create Organ Articulation Palette
  2. Add any marking

Expected Behavior: The marking appears either above the staff (for right foot markings) or below (for left foot).
Actual Behavior: The marking is placed on top of the note to which it is attached and must be dragged manually.
In addition: The markings cannot be repositioned with the arrow keys; they must be dragged. However, the arrow keys work on every other articulation.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/c8edfed1-31a8-4c5e-a135-1e108f7838a3

Offertory.zip

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

OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.4-243461245, revision: github-musescore-musescore-2232670

Regression

I was unable to check

Operating system

Windows 11

Additional context

Yes, heel and toe organ markings are not, strictly speaking, articulations. However, I would expect to interact with them the same way. (Fingering numbers can also be moved using the arrow keys.)

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.