musescore / musescore/MuseScore

Sound flags should show prior status

Open
#26,973 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Your idea

If a Sound Flag is added to a piece, subsequent Sound Flags do not show the prior selected state. For example, if Violins are set to "Classic Phrasing" in measure 1, adding an additional sound flag in measure 2 does not show that Classic Phrasing is already set. The suggestion is that the sound flag added to measure 2 would already show that Classic Phrasing is selected.

In a similar way, when a Sound Flag is first added the default status of the sound should be preselected. Again using Violin as an example, the first instance of a Sound Flag should show Modify Sound set to "Standard" and Playing Technique set to "Ord. (default)"

Problem to be solved

In addition to clarifying the current status of a Sound Flag, this would address a related problem when playing techniques are linked to Modify Sound options. In the example described above, the blank slate offered by the Sound Flag in measure 2 includes the option for "non-legato" - which is not a valid option with Classic Phrasing. Showing the current state of the flag would eliminate the confusion of a user thinking that both options (Classic Phrasing and non-legato) could be selected at the same time. (In fact, if both are selected in this manner it's not clear whether non-legato would be ignored, or if Modify Sound would be reset back to Standard.)

Prior art

No response

Additional context

No response

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

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.

Research direction

The issue names no files, tests, or entry points; start by locating the Sound Flag editor and the state used for Modify Sound and Playing Technique. Confirm how a later flag inherits the prior selection and how defaults appear on the first flag. Done means the current and default selections are shown consistently and incompatible choices are not presented as simultaneously valid.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.