musescore / musescore/MuseScore

Print dialog has multiple issues on Windows 11 (no preview, no page numbers, window issues, etc.)

Open
#16,617 19 comments 0 reactions 1 assignee View on GitHub

@Eism is already working on this.

Since Mar 2, 2023.

blocked externally community P2 UI
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UI bug

Bug description

The Print dialog on Windows 11 has multiple issues.

  • It does not show a preview of the document
  • It does not show how many pages the document is
  • If you choose to print a custom page range, the input isn't constrained to pages in the document (although only pages actually in the document will print)
  • The Print dialog window is titled "Printing from Win32 Application. - Print" which is slightly janky
  • The print dialog windows can't be accessed from the taskbar
  • When MuseScore loses focus then gains it again, the main window goes in front of the still-open Print dialog window, sometimes making it look like the Print window closed (combined with the previous issue)

ETA March 11 2023

  • If the score is set up in Landscape, the print dialog still defaults to printing in Portrait, cutting off part of the page entirely. (Tested with an Epson ET-2803 printer)
Steps to reproduce
  1. Open a score
  2. Go to File > Print or press Ctrl + P
  3. See error.
Screenshots/Screen recordings

image

image

https://user-images.githubusercontent.com/91428485/222299795-101bef67-4e61-4d9e-890a-8a69296d82e6.mp4

MuseScore Version

MuseScore version (64-bit): 4.0.2-230551516, revision: github-musescore-musescore-d23f054

Regression

Yes, this used to work in a previous version of Musescore 4.x

Operating system

Windows 11 Home, version 22H2, OS build 22621.1265

Additional context

Context about "Regression": This used to work in MuseScore 3 and MuseScore 4, but no longer works in EITHER MuseScore 3 or 4, meaning this was likely caused by a Windows update.

I have no idea how much of this issue can actually be fixed on the MuseScore end of if some of this is just janky Windows behavior that can't be fixed by MuseScore.

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.