Suggestion to adopt existing chord symbols (if present) when adding fret diagrams
Reported version
3.5
Priority
P2 - Medium
Type
Functional
Frequency
Once
Severity
S5 - Suggestion
Reproducibility
Always
Status
active
Regression
Yes
Workaround
No
Project
OS: macOS High Sierra (10.13),
Arch.: x86_64, MuseScore version (64-bit): 3.5.0.27580,
revision: b5add95
Chord Symbol is sticked to Fretboard Diagram already when I put them from palette.
It was not in the case in v3.4.2
Problem;
If I decide to put Fretboard Diagram after entering Chord Symbols,
Chord Symbols are duplicated.
| Attachment | Size |
|---|---|
| chord.jpg | 23.03 KB |
Comments
The problem is less the fact that the chord symbols are taken from the palette now (this is rather a fixed bug), but more the fact that it now also takes an existing chord symbol atop.
Hmm, the palette doesn't show the chord symbols (other that in a toolTip), not in 3.4.2 nor in 3.5, so maybe indeed it shouldn't put it into the score?
Or shows them in the palette too?
Next question is which is to win in case of such conflicts? Probably the explicit one over the one 'inherited' from the diagram.
In reply to The problem is less the fact… by Jojo-Schmitz
I thought it’s a nice idea to put chord symbols together with diagrams when put them into score.
I don’t think it’s need to show them in the diagrams palattes(shows in a Tool Tip is sufficient)
Which to win in case of duplicatate? umm.. probably previous one which already notated in the score?
I guess many people write chord symbols first then diagrams.
Currently this is by design, it's a very nice improvement that you don't have to manually enter chord symbols anymore. But it would be an additional nice improvement if, when adding a fret diagram, we simply "adopted" an existing chord symbol rather than adding a new one.