Windows 10: MuseScore blocked by hidden dialog for preferences
Reported version
3.5
Type
Graphical (UI)
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
in Windows 10 start musescore 3.5.0 (just downloaded, reset to factory settings). Bring up the dialogue for preferences and make some changes. The Window is too big to show the apply button. Grab the window top border with the mouse and drag it downwards. This makes the window disappear and musescore is blocked. It can only be killed by the task manager.
Fix version
3.6.0
Comments
You will need to use the -D option from the command line to make everything smaller. MuseScore isn't properly detecting your screen size for some reason. See https://musescore.org/en/handbook/command-line-options
Or reduce the scaling option in your display settings
Both proposals did not succeed. Only when I reduce my Text size from 150% to 100% in Windows then the preferences window shrinks to a usable size. This is a workaround but no solution.
Other Windows that are too big for my screen could be changed in size, i.e. dragging the top border down and move the window up afterwards. The dialogue window for preferences is the only one which does not allow for this. It seems to have a fixed size by no reason.
It has a certain minimum size due to the contett of at laste one tab. And It is the Canvas tab that is the limiting factor here. I believe the Zoom section is what changed (read: grew) between 3.4.2 and 3.5.0, but I'm not 100% sure
This is a problem for me too. It would be fine if the settings window had a vertical scrollbar, or indeed if the buttons were moved up into the large area of blank space above them. When attempting to resize the window it vanishes but is still modal, so mouse click and key strokes result in beeps. It can be closed by Ctrl-F4 but if opened again it retains its faulty state.
This bug is also discussed here:
#311868: Adjusting height of "Preferences" causes it to go off-screen on some monitors
Still the case with 3.6 Beta? See [ #306644]
In reply to Still the case with 3.6 Beta… by Jojo-Schmitz
The 3.6 Beta release seems to have fixed this - many thanks! It also fixes a similar problem with the Preferences window.
Automatically closed -- issue fixed for 2 weeks with no activity.