musescore / musescore/MuseScore
Wrong viewing scale after reconnecting extended display
@Eism is already working on this.
Since Jun 24, 2023.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Other type of issue
Bug description
When using secondary display, once disconnected and reconnect the display, MuseScore window is recovered at the original position, however the menu, side pallets and main score pane are wrong position and wrong scale.
My PC's default and recommended scale is 150% (over 100% is very common at recent devices I think). When I tried at 100% scale of the main display and did the same procedure, the window was the same scale as the original and that is my expectation.
Steps to reproduce
Using a secondary display as extended, and MuseScore window is at the secondary display.
- disconnect the second display
- re-connect the second display
- then the window was reset at the original position at the second display, and the view of menu, side pallets and main pain of socore are wrong position and scale.
- when drag to first display, then the window refreshed as right position and scale (without dropping it). When move back to second display then the window is correct viewing scale, and all viewing are recovered as original.
Screenshots/Screen recordings
MuseScore Version
OS: Windows 10 Version 2009, Arch.: x86_64, MuseScore version (64-bit): 4.0.2-230651553, revision: github-musescore-musescore-dbe7c6d
Regression
I don't know
Operating system
Edition Windows 11 Home Version 22H2 Installed on 6/2/2023 OS build 22621.1848 Serial number 007937230257 Experience Windows Feature Experience Pack 1000.22642.1000.0
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.