Timewise Delete doesn't behave the same on last chordrest of a measure
In the nightly build, revision 7f9585a, the current behavior of the Timewise Delete command (Ctrl+Del) removes all beats in a selection, discussed at length on this page . The command works as intended for a range, even if the range contains only a single note or rest. However, if a single notehead or rest is selected without the range box around it, (hereby referred to as a "noterest"), it exhibits two distinct behaviors:
If a "noterest" is selected that is not the last noterest a measure, then the command works as above. E.g. This:
Becomes this when Ctrl+Del is pressed:
However, if the last noterest in a measure is selected, then nothing happens. E.g. In this case:
Pressing Ctrl+Del has no effect. This is true even when the last noterest is also the first noterest.
Technical information:
Operating System: Windows 10 (64x)
3.0 Nightly Build Version: 7f9585a
Attachment | Size |
---|---|
timewise-del (1).PNG | 11.63 KB |
timewise-del (2).PNG | 10.99 KB |
timewise-del (3).PNG | 12.45 KB |
Comments
Confirmed, but not sure about the expected behavior.
In reply to Confirmed, but not sure… by Anatoly-os
Its a bug. Actually the implementation of the functionality is not complete.
See https://github.com/musescore/MuseScore/pull/3804, which fixes another issue, but also this one.
Fixed in branch master, commit 77b1da781c
fix #274117: Crash on timewise delete of tuplet
Also, fix #137821: Timewise Delete doesn't behave the same on last chordrest of a measure
Automatically closed -- issue fixed for 2 weeks with no activity.