musescore / musescore/MuseScore

Sync vertical frame text with Project Properties

Open
#33,048 0 comments 0 reactions 1 assignee View on GitHub

@avvvvve is already working on this.

Since May 26, 2026.

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

Description

Your idea

Add a "Sync" checkbox next to each field in the Project Properties dialog that has a corresponding VBox text element (see mockup below). When enabled, changes to the project property update the VBox text, and editing the VBox text updates the project property.

Image

Fields that would have a Sync checkbox:

Project Property VBox TextStyleType Addable from UI menu
Work title TITLE Yes (Add > Text > Title)
Subtitle SUBTITLE Yes (Add > Text > Subtitle)
Composer COMPOSER Yes (Add > Text > Composer)
Lyricist LYRICIST Yes (Add > Text > Lyricist)

Behavior:

  • Sync ON + edit in Project Properties: the VBox text updates to match
  • Sync ON + edit VBox text in the score: the project property updates to match
  • Sync OFF: current behavior, both are independent
  • Default for new scores: Sync ON for fields populated by the New Score wizard
  • Existing scores: Sync OFF (backward compatible)
  • Multiple elements: since the VBox can contain multiple elements of the same type (e.g. two TITLE texts), sync applies to the first element of that type
Problem to be solved

VBox text elements (Title, Subtitle, Composer, Lyricist) and project properties (workTitle, subtitle, composer, lyricist) are populated together only at score creation time. After that they are completely independent: editing the title in the VBox does not update Project Properties, and changing Project Properties does not update the VBox text. Users must update both locations manually, which is confusing and error prone.

Headers/footers already solve this by referencing metaTags via $:workTitle: tokens. The title frame needs a similar mechanism, with the added complexity of supporting in-place editing.

Prior art

Forum discussions:

Related GitHub issues:

  • #17007: Updating score properties via dialog does not update the score in the WYSIWYG editor (labeled as regression from MS3)
  • #28144: Include score metadata (title, composer, copyright) as PDF metadata on export (metadata out of sync causes wrong PDF metadata)
  • #33047: Plugin API: add getText() to read VBox title frame text (plugin side of this problem)
Additional context

This approach preserves backward compatibility (existing scores keep independent text), reuses the metaTag system as single source of truth, and gives users explicit control over which fields are linked.

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.