empty palettes in current cvs on MacOS
On MacOS 10.13.6 an empty window is displayed for both the Basic and Advanced palettes. The window shows the "Palettes" label and sizing & dismissal tools, but nothing else. Master palette works ok. Problem has been present for the last few iterations of CVS, but is not seen in released version 3.30.24090, which has correct palette behavior.
Comments
CVS? You mean Git(Hub)?
In reply to CVS? by Jojo-Schmitz
sorry. yes, I mean git
In reply to sorry. yes, I mean git by dtaber666
So the actual released 3.3.0 works, but subsequent (3.3.1) development builds don't?
In reply to So the actual released 3.3… by Jojo-Schmitz
That is correct.
Do you test nightly builds or build MuseScore from the source code yourself? Also, do I understand correctly that released version 3.30.24090 is the one downloaded from musescore.org, not self-built one?
I am experiencing the same issue with my local builds on macOS 10.15. In order for the palettes to appear, I have to select "Reload QML code" from the Debug menu. This menu is not available in release builds, but fortunately the official builds do not have this problem.
In reply to I am experiencing the same… by mattmcclinch
That is a good hint that there might be a required initialisation procedure that is not being called.
Nightly builds showing correct behaviour are linked to qt 5.9. My local builds that fail to display palettes use qt 5.12 or 5.13. So something changed between qt 5.9 and 5.12 that poses a problem for musescore on Mac.
In reply to Nightly builds showing… by dtaber666
As far as I know we don't support use of anything except Qt 5.9 on macOS, not surprising if it doesn't work. So install 5.9 (side by side with 5.12 if you like) and use that in your local builds.
In reply to As far as I know we don't… by Marc Sabatella
Qt 5.12 should work, and is supported, earlier MuseScore versions for Mac used it, but we fell back to 5.9 in order to be able to support macOS 10.10 and 10.11.
But apparently 5.12 has a bug resulting in those empty palettes
In reply to Qt 5.12 should work, and is… by Jojo-Schmitz
It has been suggested that the version of Qt may have something to do with this, but as far as I am concerned, it is still only a hypothesis. I am not sure what is causing the problem, but I do know that this patch solves it, at least for me.
In reply to It has been suggested that… by mattmcclinch
Patch restores correct palette behaviour for me using Qt 5.13, MacOS 10.13.6 as well.
In reply to It has been suggested that… by mattmcclinch
Are you going to PR it?
In reply to Are you going to PR it? by Jojo-Schmitz
I just PR'ed a modified version of the patch. It essentially does the same thing, but only if errors occur the first time. See https://github.com/musescore/MuseScore/pull/5466.