musescore / musescore/MuseScore

Restore Print button to Shortcuts

Open
#25,856 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

In prior version (v3) of MuseScore there was a Print button on the Shortcuts display to print a listing (report) of shortcut names + key assignment, either to a printer or PDF. For some reason this option was not carried over to v4 and should be. The only option now is to Export to an .xml file, which is useless for simple documentation of shortcuts, especially if the user adds/customizes shortcuts. The code for printing must exist in the prior v3 code; please restore it to v4. (see screenshot, lower right-hand corner)
Screenshot (806)

Problem to be solved

An .xml file is useless for documentation of the shortcuts list. The simple report PDF (not xml code) was convertible to Word or Excel for documenting planned and implemented personal customizations and is necessary for efficient transfer to the newer version.

Prior art

No response

Additional context

No response

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

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

Compare the prior MuseScore v3 Shortcuts display with the v4 Shortcuts display, focusing on the removed Print option and the existing XML export. Restore equivalent printing or PDF output for the shortcuts list, including customized shortcuts, and verify that the resulting report is usable for documentation.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.