musescore / musescore/MuseScore

$m (Last modification time) updates when file isn't modified

Open
#28,136 1 comment 0 reactions 1 assignee View on GitHub

@cbjeukendrup is already working on this.

Since May 27, 2025.

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

Description

Issue type

Other type of issue

Description with steps to reproduce
Steps to reproduce:
  1. Open a new default score (Home, Scores, New score, Create from template, Done).
  2. Go to Format > Style... > Header & footer.
  3. Enable "Show on first page", and disable "Different odd/even pages".
  4. Enter $m in one of the header fields, and click OK.
  5. With the trackpad (or scroll wheel, etc.), scroll/pan around the score a few times, but don't enter any notes or otherwise modify the score.
Observed behavior:

The seconds in the header time update to the current time each time the user stops scrolling.

Expected behavior:

The "Last modification time" should not change unless the file has actually been modified.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/4529a73e-1748-4b39-8236-838dcaa4f27f

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

OS: Ubuntu 22.04.5 LTS, Arch.: x86_64, MuseScore Studio version (64-bit): 4.6.0-251440316, revision: github-musescore-musescore-42be613

Regression

I was unable to check

Operating system

Ubuntu 22.04.5

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.