Palettes not working in newest version 3.3, Windows 10

• Nov 1, 2019 - 19:30
Reported version
P0 - Critical
Graphical (UI)
S3 - Major
needs info

Bring up musescore.
Choose basic workspace or create custom
Select Palettes from view. Window opens with large blank area on top, and palette list on bottom with add ond search.

nothing here respondes at all.


Title Pallettes not working in newest version Palettes not working in newest version
Frequency Many Once
Reported version 3.2 3.x-dev

In reply to by cadiz1

It makes it worse. an empty panel appears on the left. The View menu has the Palettes and inspector checked. If you unclick palettes, the panel disappears, but re-appears if you re-click it.
It also lost the history of my scores (I assume they are somewhere. )

As I described here:
It's a programmers issue, I think... The Palettes toolbar is resizable and is working. A programmer who had made this part of the project must re-code the whole Palettes with top alignment. I think this would help. In my reply I attached a GIF to visualize the problem and demonstrate that the solution what I suggest got a sense.

In reply to by kjcbq

I agree with kjcbq, sizing and resizing of windows is a problem, when 2 different screens are in use.
I see this problem with most windows since MuseScore 3.2.

My screens: The main screen is the notebook screen, 1920 x 1080, used in landscape mode. The second screen is a 1024 x 1280 monitor, used in portrait mode.

Since Version 1.x MuseScore runs on my second screen. This is very helpful, because I can edit my scores without vertical scrolling.
Before 3.2 there where only minor sizing problems, all easily tolerable.

Things changed with 3.2. Nearly every call to a window shows another size, mostly to wide and to high. Even so wide and so high, that the border of the window is outside the screen.
Sometimes so dimensioned, that the buttons are not visible. A real problem, hard to manage!
Only a manual resize of these windows can help.

Now, in 3.3 The pallette-sidebar was changed to a window and got similar problems. Now, because the palette is so important in editing mode, this is very annoying.

I don't want to fill up the forum with pictures and pictures. But if more infos are necessary, please ask for them.
Best regards,

Frequency Many Few

Just throwing in my random thoughts:

Given how the widget is rendered incorrectly-scaled and aligned to the bottom-left corner but it detects cursor position like it's properly scaled, I'm taking a guess that the new palette is made in QML embedded in a QWidget but with an incorrect devicePixelRatio applied somewhere in the tree. (QML uses OpenGL and a wrong OpenGL viewport size explains why it's aligned to the bottom and not the top.)

In reply to by edbridge

Taking the clue from other comments I moved the window in which MuseScore 3 is executing from my secondary monitor (big monitor, less resolution) to my laptop screen, and it works as expected! So the problem I have been experiencing is due to it operating on a secondary monitor with different properties!
I would think this would give a clue as to how to fix it.

It now makes it more usable.

In reply to by edbridge

Yes. Now I use it on the same way. The program is runnig on the big screen and the Palettes toolbar as a floating panel on the laptop screen.
But as edbridge says I don't agree that now it makes (this bug) it more usable. One another problem so that if I arrange something from a PDF sheetmusic (that is placed on the little screen) I must everytime click behind the Palettes. Why wasn't this problem in the previous version? It was more comfortable to work with it. I'm using Musescore years ago by this way with a co-monitor to my laptop. I think that the Palettes toolbar is best placed within the program window when somebody using a big screen. That's why we using the big screen.
It's a programmers issue.

Just upgraded to version, revision 4761df6. I'm a longtime user of musescore. Although I'm not a programmer and can't therefore pretend to offer any insights in this area, I have been a software trainer for half my life and have identified the following:
I use a Microsoft Surface Pro 4 running Windows 10 Pro. Processor is Intel i7-7660U CPU @ 2.50 GHz with 8GB memory.
Screen resolution is set to the recommended 2736 x 1824 with scaling set at 200%.
When displayed on this screen, everything works perfectly well.
However, I also have a BenQ LCD external monitor running an extended desktop at 3840 x 2160 with scaling set to 150%.
When I move musescore onto this screen everything in the palette disappears - but ONLY while the palette is docked to the side of the screen.
If I undock the palette to make it a floating pane, everything reappears and works as it should.
I have also tried changing the setup from extended desktop to duplicated displays and in this scenario everything also works properly.
I offer this as a potential work around until the problem is resolved. While not a perfect solution it does at least allow me to continue using my larger screen for score creation and editing.
I have also experimented with adjustments to the scaling options but nothing other than using a floating palette on the extended desktop makes any difference.
With kind regards to all the developers and my fellow users,
Kevin O'Kelly

Was there a solution for this that I missed?
I am on version, Window 10 Pro x64.
I am still having the issue on the monitors that are connected to the nVidia Quadro P4000
Not on the Intel Iris Pro Graphics P580

You mean the palette is still way to small?
If so: You can scale it up in that version in Edit > Preferences > Advanced > application/PaletteScale. Does that help?
If not: what else is the problem?

If I move the app to my laptop screen, I can make it useable. Back on the bigger (useable screens) the palette can be seen, but nothing can be selected from it.
I just tried an experiment of moving the mouse slowly over the palette to see if anything might show up. If I hover over the right triangle to expand “Time Signatures” I can see the tip “Treble clef”, If I hover the mouse over “Time Signatures” I get the help tip “Bass clef”. There are more, but you can get the point.