Style settings for ornament accidentals

Open
#25,193 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
design, desktop

Research direction

The issue does not name files, tests, or entry points. Start by locating ornament accidental rendering and the Style settings and Properties panel code; done means accidentals can be resized and repositioned locally and score-wide, with an option to place trill accidentals beside the tr symbol.

Written by the indexing model from the issue text.

Description

feature request
Your idea
  1. Allow changing the scaling/size and position of ornament accidentals, both locally (select one specific accidentel then modify it in the Properties panel) and score-wise (in Style settings).
  2. Add a new style where the trill/trill line accidental is placed right next to the tr symbol.
Problem to be solved
  1. Currently, accidentals on ornaments are scaled down to 60% of their normal size, which may appear a bit too small on small staves or full scores. In addition, the accidentals are a bit too far away from the ornament symbols, especially on the trill tr, it would be better if we can modify the size and position of them.
    image
    Here is an example of a traditional hand-engraved score, note that the natural symbol is placed a little to the right to avoid collision with the t ascender.
    image
  2. In some old publications, the trill/trill line accidentals are placed right next to the tr symbols, which is also helpful to save vertical space in cramped layout. It would be nice if we can have this style as well.
    image
Prior art

No response

Additional context

The workaround is not difficult thanks to the recently added symbol scaling feature. You just need to manually add the accidentals as symbols from the Master pallette and then carefully adjusting them.

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests
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.