Create a tuplet on a selected mmrest leads to corruption
2.1 version 871c8ce/ Windows10
1) New score with part, eg: mmrest tuplet.mscz
2) View part
- Your aim is to begin by a tuplet. But let's say you are a bit tired or in a rush or by discover the programm (in my case: second one, by testing something) :)
3) Select the mmrest (or the range selection, no matter)
4) Ctrl + 3
Result: you say... oops! Unexpected.
5) then type 5-> again Ctrl + 3 (You forgot to undoing...)
You say: whew! And
6) Enter your tuplet
7) Save/Close/Reload:
mmrest tuplet save.mscz
Result: corruption, which leads to bad things of course (nevertheless, the corruption is visible before save, in main score, measures 11 and 22)
- Many other related scenarios, in particular after deletion of the tuplet: satb.mscz
So, the score is already corrupted -> ignore -> cut the tuplet -> bad things type measure 0/1
Other result:
- In any case, the main point is the sequence of steps # 3 and #4
Comments
An easy fix would be to simply disable this operation. Given that it isn't really clear what the expected results would be anyhow, that's probably the best option.
Agreed
See https://github.com/musescore/MuseScore/pull/3216
This patch is merged since yesterday: https://github.com/musescore/MuseScore/pull/3216/files
So, don't know why this issue has not been marked as fixed.
Fixed in master, but not in branch 2.2 though.
Typo in my commit message kept this from being marked fixed, but since it's still open for 2.2, I guess that's OK for now :-)
Hmm, maybe the PR isn't mergeable for 2.2, as it hits code that is different between 2.2 and master? Also some of the same code involved with #202271: Copy-paste sextuplets/octuplets and their removal leads to corruption
Fix ported to 2.2 as part of PR https://github.com/musescore/MuseScore/pull/3410
Fixed in branch 2.2, commit ba54f4509e
fix #224781: corruption creating tuplet on mmrest (porting ab28b7e from MarcSabatella into 2.2)
Automatically closed -- issue fixed for 2 weeks with no activity.