musescore / musescore/MuseScore

Resetting offset should not affect minimum distance style settings

Open
#33,002 3 comments 1 reaction 1 assignee View on GitHub

A pull request for this has already been merged.

  • #34419 by @miiizen — merged
engraving P2
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce
  1. Add some accents to notes in the score (or any other element with a configurable 'Minimum distance' property in Properties > Appearance).
    • See that the default minimum distance for accents is 0.4sp.
  2. (This step is optional) In Format > Style > Articulations & ornaments, increase 'Minimum vertical distance' to 1.5 to exaggerate the difference.
  3. Select an accent, and in Properties > Appearance change its vertical offset.
  4. Reset the offset property. Upon doing so, see that 'Minimum distance' changes from 1.5 to 0.35, which is neither the correct style setting nor the original default minimum distance. It then becomes resettable, even though I haven't manually changed it.

Expected result: When resetting offset, minimum distance should not be affected.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/dbab8826-f4c9-4679-b818-297822c902af

In which versions of MuseScore Studio is this issue present?

4.6.5

Regression

No.

Operating system

macOS 15

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.