musescore / musescore/MuseScore

When changing show options (show invisible, show formatting etc.), score is not marked as changed

Open
#28,089 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P2
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
  1. Uncheck some options in View>Show>
  2. Close score
  3. Open score
  4. Show options are not saved
  5. Uncheck some options again
  6. Make some changes in score
  7. Close
  8. In 'Do you want to save..' dialog, click Save
  9. Open score
  10. Now Show options are preserved fine
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/7bd0a65f-9481-4c78-8849-60a0275a0ec6

What is the latest version of MuseScore Studio where this issue is present?

4.6 nightly

Regression

No.

Operating system

Windows 10

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

Start by reproducing the behavior through View>Show, then close and reopen a score without making score changes and compare it with the save-dialog path. Trace the score close/save entry points involved in persisting show options. Done means changing show options marks the score as changed and preserves them after choosing Save.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.