Skip to content

Conversation

@iveshenry18
Copy link
Contributor

Resolves: ENG-9: Copyright info appears on every page

Currently, MuseScore displays copyright metadata in a centered footer by default.
This results in the information being displayed on every page, which
is inconsistent with many published scores.

This commit hides the footers on XML import and rather creates a VBox,
populates it with the copyright metadata, and places it at the bottom
of the first page (either below the first explicit pagebreak, or below
the last system of the first page after an initial layout).

  • I signed CLA
  • I made sure the code in the PR follows the coding rules
  • I made sure the code compiles on my machine
  • I made sure there are no unnecessary changes in the code
  • I made sure the title of the PR reflects the core meaning of the issue you are solving
  • I made sure the commit message(s) contain a description and answer the question "Why do those changes fix that particular issue?" or "Why are those changes really necessary as improvements?"
  • I made sure the commit message title starts with "fix #424242:" if there is a related issue
  • I created the test (mtest, vtest, script test) to verify the changes I made

@iveshenry18 iveshenry18 force-pushed the ENG-9-copyright-info branch from e848b23 to 19e06c7 Compare July 20, 2021 20:21
@iveshenry18 iveshenry18 force-pushed the ENG-9-copyright-info branch from 19e06c7 to 15df67c Compare July 28, 2021 16:21
Currently, MuseScore displays copyright metadata in a centered footer.
This results in the information being displayed on every page, which
is inconsistent with many published scores.

This commit hides the footers on import and rather creates a VBox,
populates it with the copyright metadata, and places it at the bottom
of the first page (either below the first explicit pagebreak, or below
the last system of the first page after an initial layout).
@iveshenry18
Copy link
Contributor Author

Changes added to #8763

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants