Chord Symbols do not add to palettes properly (TPC is missing)

Open
#18,333 3 comments 0 reactions 2 assignees View on GitHub

@DmitryArefiev is already working on this.

Since Jun 30, 2023.

Assessment

This issue has not been assessed yet.

Description

needs review palettes
Issue type

Other type of issue

Bug description

No response

Steps to reproduce
  1. New Score
  2. Add a Chord Symbol, for example Cmaj7
  3. Add symbol to palette (Ctrl+Shift+Drag)
    Result: instead of showing Cmaj7 on the cell information of the palette, the result is "maj7"

This was also the case in 3.x behavior. Some how the TPC information is omitted in the process.

Adding chord symbols to a palette doesn't seem to be very common based on forum use over the years, but the idea is to be able to make palette(s) of chords to enable placing them onto a score via mouse as an alternative to text entry with manual typing. I've got a custom 3.x build that allows for this, all the while selecting the next ChordRest after placement to facilitate mouse entry. Niche case, I presume, but seems at least worth fixing the lack of tonal-pitch of a chord symbol in the palettes.

Screenshots/Screen recordings

Here's a demonstration of the problem:

https://github.com/musescore/MuseScore/assets/7139517/be1a1d6e-f1ea-4c7a-b5e5-68b8891f5c0e

Niche case of continual entry is what I have the ability to do, and maybe that might be considered worth implementing in 4? A quick example is given (It's nice not having to type it in given a reasonable palette setup):

https://github.com/musescore/MuseScore/assets/7139517/3f052054-253b-48c7-b727-60b680db1072

MuseScore Version

4.1 Beta

Regression

No.

Operating system

Linux XFCE

Additional context

By the way, in 3.6's code, the Harmony::Render function is used to concoct the display of a chord symbol.
When dropping/adding a Chord Symbol into the palette area,

RenderActionType::NOTE/ACCIDENTAL

is never an actual case, but only SET (which doesn't handle the TPC)

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.