Incorrect display of workspaces after installing MDL

• Dec 5, 2018 - 16:04
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
Yes
Workaround
No
Project
Tags

The order of the list of workspaces in Version 3.0 beta is listed as Basic, Advanced, Advanced, Basic (and MDL).
The workspaces appear twice in the list.
This is probably not the desired result.
Capture.jpg


Comments

After performing a factory reset, this issue no longer occurs. Maybe it has something to do with the drumline extension (which I installed after I started the program for the first time).

In reply to by JohnJ1995

To test this reinstall MDL to see if it comes back.

Frequency is related to how many times it's been reported. Reproducibility tells when you can force the bug to be seen. If it comes back when you install MDL, it needs to be set to always.

Title Issue with the list of workspaces Issues after installing MDL
Reproducibility Once Always

This issue is indeed related to the MDL installation. I have also confirmed that after I install MDL and close Musescore, it cannot be opened again without a factory reset (will remain at the splash screen).
Additionally, Musescore closed unexpectedly when uninstalling MDL.

In reply to by JohnJ1995

Title Issues after installing MDL Cannot open MuseScore after installing MDL.
Severity S3 - Major S1 - Blocker

I changed the title to indicate the worst of the problem installing MDL. Installing MDL seems to cause more than one problem.

Status active needs info
Priority P1 - High

"will remain at the splash screen" - not sure this is actually a crash. MDL is known to be loaded for 2-5 minutes depending on your machine configs. Could you please wait a bit longer and confirm that MuseScore cannot actually start with MDL installed.

Title Cannot open MuseScore after installing MDL. Issues with MDL.
Severity S1 - Blocker S3 - Major
Status needs info active

This is not a crash. MuseScore did eventually start properly. I have modified this issue accordingly.