musescore / musescore/MuseScore

MS 4 Virtual Piano does not return to normal size when Mixer menu is closed

Open
#17,634 3 comments 1 reaction 2 assignees View on GitHub

Nobody has claimed this yet.

mixer P2 UI
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

General playback bug

Bug description

Sorry if this was already reported in the past. I did not locate any post about it.

In MS 3.6, when I open the mixer with the virtual piano keyboard active, the Mixer menu overlays on top of the score. I can then change things. When I close the mixer, the menu goes away & the screen view returns to normal, with the score fully visible and ready to work on, and the piano keyboard back to its small size near the bottom.

Before mixer:

image

With Mixer open:

image

After Mixer menu closes. Scene returns to "Normal":

image

In MS4, when I open the mixer with the virtual piano active, make changes, then close it, the overlay simply turns to black with the keyboard blocking most of the score. It does not resize. I have to manually grab the edges of the menu and drag it down and resize it to return to a workable score. See below for an example:

Screenshot 3 - the score before the mixer is opened:

image

Screenshot 4 - the score when the mixer menu is open and overlaid onto the score

image

Screenshot 5 - the score after the mixer is closed. Notice that the view of the score is almost obscured. I have to click on the scene, locate the edges of the now black menu, & drag things down to restore my screen to a workable view.

image

This should not be. The view should simply return to "normal", as done in MS 3.6. Please fix. Marc Sabatella agrees it is a bug and suggested I post it here. Thanks

Steps to reproduce
  1. In MS4, activate Virtual Piano and shrink to small size near the bottom so you can work on the score.
  2. Open the Mixer menu
  3. Close mixer menu. The virtual piano screen is now so large you cannot see the score. It has to be manually shrunk back down.
Screenshots/Screen recordings

See above screenshots

MuseScore Version

MS 4.0.2

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

Windows 10 Home

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.