Context menu remains on screen after selecting instrument sound within mixer
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the linked recording around 19:14 and reproducing the mixer instrument dropdown steps on Windows 10. Check the available AppData log files if provided and investigate the mixer menu behavior. Done means selecting an instrument closes the menu cleanly and no menu artifact remains after closing the mixer.
Written by the indexing model from the issue text.
Description
Issue type
UX/Interaction bug (incorrect behaviour)
Bug description
I was changing Violin (and Viola) from group to solo instrument within MuseScore 4.1.1 (my score was created in MuseScore 2, updated in MuseScore 3.4 and then imported into MuseScore 4) and as you can see in my video, there is a nasty bug here, where the context menu remains on screen.
The behaviour I saw is that the menu initially fails to appear, and on second click, the dropdown appears but is frozen-a third click opens a second dropdown, and this works. Upon selection, the menu closes as expected, revealing the frozen dropdown from the 2nd click still on the screen. Closing the mixer, the dropdown remains on the screen as some sort of orphaned artifact.
I was reviewing MuseScore (3 to 4) at the time, so I managed to capture this bug in my recording. I decided not to edit it out because I feel it may be useful here for you guys. (I actually encounter a rather more serious bug after closing the app to reload and remove that orphaned menu... I don't know if it is related, but the only way to fix the second issue was to re-install - I mention it here as I wonder if it's related).
Anyway, here is my video, and I've included the time stamp of the bug in the URL (Its around 19mins 14seconds FYI - I check each drop down within the mixer and it breaks on the Viola/Violin 2 - I actually had it happen twice, once on each. The serious splashscreen issue didn't happen first time around, but did on this second run, and that happens to be the one I recorded)
Reviewing MuseScore 4 with my arrangement of Auld Lang Syne, and encounter a UI bug
Steps to reproduce
- Open the mixer
- Open a drop down to change the instrument sound
- The menu is frozen and cannot be used.
- Close the mixer, the menu remains on screen
I cannot reproduce this bug subsequently - I don't know what caused it unfortunately; I am a software developer and am really sorry as I know reproducing these things is quite important for investigating! I do have the log files from AppData if they are useful to you. I saved them before uninstalling (not to fix this bug, but to fix a nasty Splash Screen hanging issue. QT is causing an infinite loop on startup, some ImplicitWidth is set to null? I wonder if its related to this menu. MuseScore 4 was working perfectly for me until this menu happened. Then when I tried to reload the software, it hangs on the splash screen and never spawns the UI. So its not the splash screen bug that was reported in Jan 2023, its a new splash screen bug).
Screenshots/Screen recordings
https://youtube.com/video/bRKUxV2r3Ps&t=19m14s
MuseScore Version
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.1.1-232071203, revision: github-musescore-musescore-e4d1ddf
Regression
I don't know
Operating system
Windows 10 Pro x64
Additional context
No response
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
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.
More from musescore/MuseScore
-
engraving P3 UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
needs design
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
community P3 UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
regression nightly UX/interaction
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in musescore/MuseScore
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·