An undo bug, and how then to crash MuseScore reliably ;-)
This is not an important bug, and not an important crash. I just want to record it.
I have attached a gif that shows the sequence with enormous speed - here are the steps:
- Open a fresh Musescore 3.6.2.
- Esc to close Startcenter.
- N for input mode.
- C, B, A, G to add four notes.
- Esc to leave input mode.
- Now select the four notes as a list (not a range) by Ctrl-clicking on them out of order (e.g. B, C, A, G, G again to reselect it).
- Go to the "lines" palette and click on slur. You will get four individual slurs, from C to B, B to A, A to G, and G to the next full rest.
- Now, press Ctrl-Z. Only one slur vanishes (this is the bug).
- Press Ctrl-Z four more times. The notes vanish one by one, but 3 slurs remain hanging around.
- Esc (for some reason, we are in input mode again - we need to leave it).
- Grab the leftmost slur with the mouse and pull it around -> Crash.
H.M.
Attachment | Size |
---|---|
CrashMusescore.gif | 1.51 MB |
Comments
Hmm, might be related to https://musescore.org/en/node/333979, might explain how the problem there got introduced?