musescore/MuseScore

Window and Cursor behaviour in 4.4.1 (window header is broken, Windows only)

DmitryArefiev opened this issue · 3 comments

DmitryArefiev commented

Issue type

UI bug (incorrect info or interface appearance)

Description with steps to reproduce

https://musescore.org/en/node/368201

On operating MS 4.4.1 for the first time I am getting some crazy behaviour with my screen - the system is unoperable because half the buttons are missing in full screen mode and in order to effect a button I have to click a centimetre above it. The only way of exiting was to CTRL ALT DEL.

Also, when I did manage to play through a score the progress mark was a note or so behind the music. But that's a minor issue in the grand scheme of things.
Windows 10 by the way. No problems with previous version of MS.

Supporting files, videos and screenshots

You will see that there is a margin above the commands, and it is as if the musescore stuff has "slipped down" the screen. So when I click on View for example, nothing happens, but if I click slightly above View, the button responds.
All my other computer facilities behave as normal:

Capture_0

Also attached is the result of maximising the MS window - there appears to be a transparent top edge, and I have to click above the buttons (inside the transparent area!) to get a response:

Capture full

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

4.4.1

Regression

Yes, this works in the latest released version and is broken in the nightly builds

Operating system

Windows 10

Additional context

No response

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
cbjeukendrup commented

Previous instances of this problem:

  • #22369 (occurred after switching to Qt 6; was fixed by removing QQuickWindow::setGraphicsApi(QSGRendererInterface::OpenGL))
  • #8270 (occurred even with Qt 5; was fixed by adding QCoreApplication::setAttribute(Qt::AA_UseOpenGLES); (which does nothing anymore in Qt 6) and QT_OPENGL_BUGLIST)
cbjeukendrup commented

Diagnostic files from the author of that .org forum post:
DIagnostic zip file.zip

bkunda commented

This doesn't seem to be a regression to nightly if it is in fact broken in the current release build (4.4.1).

The "regression nightly" label should be used for "works correctly in the latest released version and is broken in the nightly builds", so unless I'm misunderstanding something, it would appear this issue is a "regression MS4" because it the functionality is in fact broken in the latest released version, right?

  • 👍1