Entering a tuplet after a time signature changing leads to a fail and a corruption

• Nov 10, 2014 - 12:25
Type
Functional
Severity
S2 - Critical
Status
closed
Project
MuseScore

Nightly, November 10 (b24f784) / Windows7

1. Open "My First Score"

2. Fill the first measure with four quarter notes

3. Always in note entry mode -> drag and drop the 3/4 TimeSignature

Result: the cursor jumps.
2jump cursor.jpg

4. In Note Entry mode always (the quarter note value is already selected), try to create a tuplet (Ctrl + 3)

Result: fail (no triplet), and worst, corruption.
3fail and corruption triplet.jpg

Final result: without triplet :(
4finale result.jpg

Additionnal note:

If you made: Exit Note entry mode before drag and drop the 3/4 TimeSig, the last quarter note of the first measure remains highlighted, and so the risk of mistake is possible (the entering of a tuplet on this last note)

other issue.jpg

Attachment Size
2jump cursor.jpg 12.33 KB
3fail and corruption triplet.jpg 12.55 KB
4finale result.jpg 17.57 KB
other issue.jpg 10.29 KB

Comments

• Nov 10, 2014 - 13:39

I do not have time to search for more today (go to my job!) , but I noticed that this issue is already in the 2.0 Beta1.

Reply

• Nov 11, 2014 - 00:11

Basic cause seems pretty obvious: the change of time signature requires re-writing all the measures from that point forward, and this means the segment the input cursor was on is no longer valid. I will try to fix by finding the segment at the same tick as the original.

Reply