MuseScore icon indicating copy to clipboard operation
MuseScore copied to clipboard

Full screen mode has some glitches (Windows)

Open FrancRos31 opened this issue 1 year ago • 12 comments

Issue type

UI bug (incorrect info or interface appearance)

Description with steps to reproduce

  1. Open the app
  2. press F11 to toggle the full screen mode, press "more" on palettes, open the menus Expected behaviour: no glitches at all Actual behaviour: glitch almost anytime (look the top of the screen)

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/a2516a5d-912a-4e24-b545-52497d555c1a

What is the latest version of MuseScore Studio where this issue is present?

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.1-242490810, revision: github-musescore-musescore-0b3dd00

Regression

I was unable to check

Operating system

Windows 10 Pro

Additional context

No response

Checklist

  • [X] This report follows the guidelines for reporting bugs and issues
  • [X] I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • [X] I have attached all requested files and information to this report
  • [X] I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

FrancRos31 avatar Sep 09 '24 14:09 FrancRos31

Could you please provide us with a bit more information?

  • Diagnostic files (go to Diagnostic > Save diagnostic files)
  • Details about your graphics hardware (GPU)

bkunda avatar Sep 10 '24 13:09 bkunda

The update to version 4.4.2 didn't change anything.

diag.zip

Here the specs of my GPU 1

FrancRos31 avatar Sep 22 '24 17:09 FrancRos31

On a first investigation, I see nothing relevant in the log files. It's most likely a Qt bug, rather than a bug in MuseScore's own code. You could try if it's fixed in the builds from #24644 (see How to download test builds from pull requests for instructions).

cbjeukendrup avatar Sep 22 '24 22:09 cbjeukendrup

Ok, I'm gonna try, thanks.

FrancRos31 avatar Sep 23 '24 16:09 FrancRos31

On a first investigation, I see nothing relevant in the log files. It's most likely a Qt bug, rather than a bug in MuseScore's own code. You could try if it's fixed in the builds from #24644 (see How to download test builds from pull requests for instructions).

This build doesn't work at all. The problem remains.

FrancRos31 avatar Sep 23 '24 17:09 FrancRos31

I can reproduce this, in all versions of 4 (not a recent regression) I suspect it has something to do with display settings / scaling, @cbjeukendrup let me know if there is any additional info I can give you

Screenshot 2024-09-30 140953

zacjansheski avatar Sep 30 '24 18:09 zacjansheski

I can reproduce this, in all versions of 4 (not a recent regression) I suspect it has something to do with display settings / scaling, @cbjeukendrup let me know if there is any additional info I can give you

Do I need to adjust some setting?

FrancRos31 avatar Sep 30 '24 19:09 FrancRos31

Probably this is a MuseScore bug, in winframelesswindowcontroller.cpp. We'll somehow need to fix that...

@FrancRos31 Could you elaborate on your comment from above about the build from https://github.com/musescore/MuseScore/pull/24644? When you try to launch it, does simply completely nothing happen? Or do you get some error message?

cbjeukendrup avatar Sep 30 '24 20:09 cbjeukendrup

No problem at all launching the build, no error messages, it works well. But what I reported here is still present, same issues. Actually I must show you something new, look at the File and Edit menus in the top bar when I simply move the cursor above the menus.

https://github.com/user-attachments/assets/09dc8f2a-e6c7-493b-8983-465dee2ee6a6

This other glitch is also present in version 4.4.2 (OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.2-242570931, revision: github-musescore-musescore-3130f97).

FrancRos31 avatar Oct 01 '24 10:10 FrancRos31

Please check the Preferences dialog in Edit menu. In normal screen it's a bit glitchy (OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.2-242570931, revision: github-musescore-musescore-3130f97).

https://github.com/user-attachments/assets/60057ab5-5a23-42c9-9195-8a33e2115eb7

This issue appears also in the build of #24644. If you need, change the title.

FrancRos31 avatar Oct 01 '24 10:10 FrancRos31

I think the white flash when a dialog is opened has a different cause. In fact, it has been logged here: https://github.com/musescore/MuseScore/issues/23472

cbjeukendrup avatar Oct 01 '24 11:10 cbjeukendrup

The issue is pretty bad when opening a new score using the shortcut Ctrl + N. In addition to the top bar, the white flash is very strong in this one.

https://github.com/user-attachments/assets/2efd9cde-df18-42b2-b2a3-5f3f298df343

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.2-242570931, revision: github-musescore-musescore-3130f97

FrancRos31 avatar Oct 16 '24 23:10 FrancRos31

Another one to the list, this time in normal mode (OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.3-242971445, revision: github-musescore-musescore-eb6b367).

Look at the glitch when moving between opened View and Add menus and Help and Diagnostic menus.

https://github.com/user-attachments/assets/25d62b7a-cda3-46e6-bd76-e68b35ab428f

FrancRos31 avatar Oct 25 '24 10:10 FrancRos31

Another one, normal and full screen mode (OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.4-243461245, revision: github-musescore-musescore-2232670).

https://github.com/user-attachments/assets/3d7239b1-ae58-420a-a2f4-8e2c9e072b03

FrancRos31 avatar Dec 16 '24 00:12 FrancRos31

I am no longer able to reproduce this in Nightly, possibly resolved by latest Qt update. @FrancRos31 please confirm

zacjansheski avatar Jun 26 '25 13:06 zacjansheski

@zacjansheski, the two issues still not fixed are definitely better on my side. Everything else is fixed, though, thank you.

https://github.com/user-attachments/assets/5ee9840b-6680-4b6d-836e-55d2322fbd32

https://github.com/user-attachments/assets/d18b9546-2ff3-4db5-b0fc-e4091bade352

https://github.com/user-attachments/assets/ec5cf9d8-8b1f-4a46-b33d-7e66aaeeaab1

In the video above (0:12), MS is freezing upon closing.

https://github.com/user-attachments/assets/fba5c9c9-585c-45a0-a361-7844a2728a53

FrancRos31 avatar Jun 26 '25 22:06 FrancRos31

@FrancRos31 thank you, I think this issue report has gotten too bloated, as it stands this is the issue:

Windows Glitch

  1. Opening and closing full screen
  2. Ctrl+N full screen

Could you please open a fresh issue with just those in the video? (I'm unable to reproduce) Then close this report.

zacjansheski avatar Jul 11 '25 17:07 zacjansheski

Closing per above comment, remaining glitches moved to #28772.

FrancRos31 avatar Jul 11 '25 22:07 FrancRos31