New Instruments creation when "Hide empty staves within systems" is on.

Open
#26,335 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Reproduce the behavior in MuseScore Studio by enabling Format>Style>Score>Hide empty staves within systems, then adding a new instrument. Determine where instrument creation and this setting intersect; done means a clear notification explains that the instrument was added but is hidden.

Written by the indexing model from the issue text.

Description

Your idea

I think when a new instrument is added something should pop up and notify the user (especially new and inexperienced ones) that the instrument has been added but will not display because the global setting "Hide empty staves within systems" is on.

Problem to be solved

I discovered a rude behavior in MSS4.44 but I suspect it may have been there for a while.
I added a new instrument. It did not show up on the score. I knew I had "Hide empty staves within systems" turned on.
(Format>Style>Score>Hide empty staves within systems)
Personally I think when a new instrument is added something should pop up and notify the user (especially new and inexperienced ones) that the instrument has been added but will not display because the global setting "Hide empty staves within systems" is on.
{OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.4-243461245, revision: github-musescore-musescore-2232670OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.4-243461245, revision: github-musescore-musescore-2232670}

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
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.