Custom workspace: most palettes have been lost
Reported version
3.0
Priority
P2 - Medium
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
Yes
Workaround
No
Project
Win 10 / MS 3.0.0, 26ad655
I copied and pasted the custom workspace from MS 2.2 (Portable) to the " … Musescore3Development > workspaces" folder. On opening MuseScore 3, most of the custom workspace palettes have been lost. See attached workspace.
| Attachment | Size |
|---|---|
| my_workspace.zip | 1.86 KB |
Comments
This looks like a version 3.x workspace, not like a version 2.x one
In reply to This looks line a version 3… by Jojo-Schmitz
He did say the version is 3.0-dev.
He also said the workspace was taken from 2.2, the one he attached doesn't seem to though
The uploaded workspace was originally created probably in 2015. Not sure what version of MS it was then. It has been added to and modified since that date. But it is an exact copy of the one working in MS 2.2 portable and MS 2.3.
OK, I've double-checked: the workspace you attached here has definitely not been last saved with MuseScore 2.x, but with a 3.x development build.
A 2.x wokspace has this:
<museScore version="2.06">your's has
<museScore version="3.01">so clearly is 3.x workspace
I've just saved an edited version of the workspace from MS 2.2 (see zip attachment). Presumably this creates a version 2.2 workspace? However, copying it over to MS 3.0.0 still gives the same result: most of the palettes have been lost.
Whatever you did, this too is a 3.x workspace.
But maybe 2.x and the 3.x workspaces are simply incompatible to one another?
In reply to Whatever you did, this too… by Jojo-Schmitz
In MS 2.2 portable, I added a tempo mark from a score to the tempo palette. Wouldn't this update the workspace to vs. 2.2? Then I uploaded a copy of the same workspace.
A 2.x workspace is a 2.x workspace, throughout all 2.x versions, all have that 2.06 file version.
Copying it across to 3.0 and running 3.0 with it, may have changed the file version to 3.01, but still not understand the internal structure.
Critical, surely, as parts of the user workspace are being lost.
I don't think 2.x workspaces are supposed to work with 3.0. It doing not surely isn't critical
@geetar could you please attach initial 2.X workspace so we could verify the structure and understand whether it is possible to support custom 2.X workspaces in 3.0 out of the box?
As requested.