"Select workspace" dropdown occupies an extra toolbar in MS3.3 RC2

• Oct 24, 2019 - 19:50
Reported version
3.2
Type
Graphical (UI)
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project

Win 7 / MS 3.3 RC2

In the RC, an extra toolbar is used to accomodate the "Select workspace" dropdown (taking up extra vertical space in the program). Is this a bug, because in the latest nightly (OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.3.0.8652, revision: 44d2b20) the "Select workspace" dropdown shares the Note input toolbar?


Comments

Severity S3 - Major S4 - Minor
Type Functional Graphical (UI)

I have seen this and keep trying to figure it out. What I think is happening is that by default it wants to share an existing toolbar, but if you then run 3.2.3, the toolbar settings get overwritten, so next time you load 3.3 you see this behavior where the workspace button no longer has a home. I won't swear that's it, but it seems most consistent with what I think I've noticed. In any case, you can always redock it where you like.

MS 3.3. RC2.

A minor issue: the dotted double line that signifies the undock zone is on the left of the program window while the "Select workspace" dropdown is on the extreme right. Could the former be moved so that it is closer to the dropdown?

Workaround No Yes

This toolbar is intended to appear exactly in the same row with Note input toolbar by default, and the issue happens only if upgrading from 3.2.3 and only in some cases (maybe if the window size was too small or perhaps an Advanced workspace was chosen). Right now I am not sure how to force Qt to make this toolbar appear at the correct place.

A workaround is available though: one can just drag the toolbar to the desired place (left edge of the toolbar can be dragged, at least on Linux).

I meant not exactly 3.2.3 version but all the previous versions, of course. The issue doesn't seem to occur always, for me that toolbar displays at the correct place although once I have seen this issue happening on my system. I am not sure which exactly conditions are needed to reproduce this issue.