Crash by changing a clef by double click
Nigthly, August 2 (9195a9f) / Windows7
1) New score for violin, 4/4.
2) Enter notes of different values, and rests or not.
3) Select the first note, or rest, of the second measure (or followings)
4) Open the Clefs Palette
5) Double-click on any clef, even the original clef.
Result: crash
Comments:
- The crash does not occur on the first measure. Only on the first note or the first rest, no matter the notes values or rest values, of the measure 2 and followings. And for all the clefs of the Palette.
- No crash with drag and drop.
| Attachment | Size |
|---|---|
| clef crash.jpg | 27.29 KB |
Comments
Actually, it *does* crash for drag & drop, *if* you drop directly onto the first note of the measure (when the note highlights) rather than dropping on the measure as a whole (when the measure highlights).
Anyhow, simple fix. forthcoming.
https://github.com/musescore/MuseScore/pull/1092
If it helps, and after several trials of earlier Nightlies, apparently the regression goes back at July 25.
Nightly, July 25 (54a97b8) and some previous: ok, works well.
Nightly, July 25 (5473249) and some next: crashes.
Fixed in 28d0cb9f3c
Thanks for the fix. But I think there is still a small problem. I can not very well identified it.
![clef.jpg]( "clef.jpg")
It seems that the last selected clef is not taken into account when moving to the second stave (system) ? Look at this picture, and the file mscz. attached. clefs change.mscz
Thanks to validate or invalidate, and open an issue if necessary. I worked too hard today! :-)
I confirm my doubts. Look at this: 2clef.mscz
Edit: It is possible that the situation returns to normal after saving and reopening the score.
I can confirm the issue you are seeing, although it's actually tricky to reproduce - simple examples seem to work just fine. It does seems unrelated to the crash, so I will open a new report with what are hopefully reliable steps to reproduce. Thanks for your diligence!
See #28826: Wrong clef at start of system. I managed to narrow it down to a few short series of steps that show different symtpoms but which hopefully relate to the same basic issue.
Automatically closed -- issue fixed for 2 weeks with no activity.