musescore / musescore/MuseScore
Dragging MuseScore between monitors sometimes makes the window very wide
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
UI bug (incorrect info or interface appearance)
Description with steps to reproduce
- Launch MuseScore Studio with an extended display (see my setup's details below)
- Drag MuseScore back and forth between the two monitors
- Observe that sometimes (with seemingly no pattern as to when it happens and doesn't) the MuseScore window becomes extremely wide and tall when moving between monitors, overflowing off of the screen.
Supporting files, videos and screenshots
https://youtu.be/7LmAgZNo-xA?t=9 (See timestamp for the first instance where it happens. As mentioned before, this bug only happens sometimes and I can't figure out what conditions are causing it to happen.)
At 1:12 you can see it happen on the other monitor for the first time in the video.
In which versions of MuseScore Studio is this issue present?
MuseScore Studio version (64-bit): 4.6.0-252730940, revision: github-musescore-musescore-7829779 (It also happened on 4.5 which was the first version I tried on this monitor setup.)
Regression
I was unable to check
Operating system
Windows 11 Home 24H2
Additional context
I have tried different conditions such as maximizing before dragging, maximizing by dragging to the top of the screen, etc. but I cannot find consistent cases where this bug happens or doesn't happen.
Information about the display setup:
- The monitor on the right-hand side is my laptop screen, which is set as the primary (1st) display.
- Resolution: 2880 x 1800
- Scale: 200%
- Actual size: 14"
- On the left-hand side: external monitor (2nd display)
- Resolution: 1920 x 1080
- Scale: 100%
- Actual size: 27"
Checklist
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
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.