musescore / musescore/MuseScore

Idling menu items not disabled

Open
#25,437 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

Open MuseScore.
Click Score under the menu bar - it opens empty workspace (no scores).
Most menu item are properly disabled, but a few remained active - though nothing could be executed:

  • View -> Toolbars and Show
  • Add - all items
  • Format -> Stretch
  • Tools -> Voices and Measures

View -> Toolbars and View -> Show should be disabled.
There are no usable active items in Add, Format and Tools; hence, these top level items could be disabled too.

Supporting files, videos and screenshots
What is the latest version of MuseScore Studio where this issue is present?

4.4.3

Regression

No.

Operating system

Windows 11

Additional context

No response

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

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

No source file or test is named. First reproduce the issue in MuseScore by opening Score with an empty workspace and checking the listed View, Add, Format, and Tools menu items. Done means unusable menu items are disabled consistently in that state.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.