Crash creating workspace
P0 - Critical
S2 - Critical
I tried to create my own workspace (crashed immediately). When it came up again, I opened the master palette to attempt to create a 4/2 signature. I created it, and could drag it, but the time sig palette would not accept it (Mac, Mojave). Can't write my song; need 4/2.
P0 priority is set for the crash scenario.
No crash for me, but this could be one of those macOS / Qt things I guess. Which version of the beta were you using, and can you repeat the crash?
Anyhow, it's normal you can't add a custom time signature to a palette unless you first create a workspace and enable editing in that palette. But you can still add the time signature directly to your score, no need to go through the palette. This is the same as 2.3.2.
In reply to No crash for me, but this… by Marc Sabatella
I said in the title, 19868. How do (and why must) one "enable editing" in a custom workspace?
(Edited) Well, now "enable editing" I found in the right-click menu is "on" (I didn't do it), and I can add it. Why is "enable editing" necessary? No, I cannot repeat the crash. Crashing switching workspaces has been previously reported.
Sorry, I didn't recognize that number as a build id, and don't know an easy way to figure out what it refers to. For the record, best way to report the exact version is to use Help / About and hit the button next to the revision field, then paste here, like this:
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 220.127.116.1128, revision: 2b25396
Probably the crash is related to the other Mac-specific UI crashes, do let us know if you can reproduce it using a recently build.
Anyhow, enable editing is indeed in the right-click menu, same as in 2.x, as documented in the Handbook under "Custom workspaces". I suspect the reason for this was to protect people against accidentally modifying the pre-defined palettes - especially accidentally deleting things from them. I think the expectation was that people would normally be preferring to create their own new palettes than modifying the predefined ones. But since custom workspaces are a pretty "advanced" feature anyhow, it's open to question whether this level of protection-from-oneself is really appropriate here.
See also #167171: Make custom palettes based upon advanced workspace default to not enable editing