musescore / musescore/MuseScore

Expanded Use of staff-level Per-Staff AutoOnOff setting for measure numbers.

Open
#31,362 0 comments 1 reaction 2 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

I would like to expand the use of the Pid::SHOW_MEASURE_NUMBERS property on Staff to work with any measure number mode as follows:

  • ABOVE_SYSTEM: If staves that are not the top staff have m_showMeasureNumbers set to On, then measure numbers would show on that staff.
  • BELOW_SYSTEM: If staves that are not the bottom staff have m_showMeasureNumbers set to On, then measure numbers would show on that staff.
  • ON_ALL_STAVES: If m_showMeasureNumbers is Off, the measure number would not be shown on that staff.
  • ON_SYSTEM_OBJECT_STAVES: unchanged

In addition, I would add this setting as a popup menu on the Staff/Part properties dialog. (Or the Advanced style properties dialog.)

Problem to be solved

While I think it is nice to have a setting that ties measure number display to the display of time sigs, tempo, etc. I do not think it should be required in order to have control over which staves display measure numbers. (When you want more than just top/bottom but less than all staves.)

Furthermore, the current UI I find to be clunky and confusing and completely not obvious. Obviously, others may not feel the same way. I can elaborate if necessary.

Prior art

What I have described is basically the equivalent of how Finale does staff-selection for measure numbers. (Leaving aside some differences that are not really applicable to this request.) Finale has no concept of ON_SYSTEM_OBJECT_STAVES for measure numbers, though.

Additional context

It appears to me that the implementation of this feature request would be a trivial modification of Staff::shouldShowMeasureNumbers. (Plus a new field on the Staff/Part properties dialog.)

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.