Crash when editing all lines and other spanners

• Jul 5, 2017 - 17:40
Reported version
3.0
Type
Functional
Severity
S2 - Critical
Status
closed
Project
MuseScore

Current 3.0 dev. 8fb09aa / Windows 10

1) "Untitled" score
2) Enter some notes
3) Add a line (slur, hairpin, volta or other)
4) Double-click, for edit mode
5) Hit arrow Up/or Down/or Right etc.

Result: crash

- Same result with all lines, and also by editing arpeggios, glissandos, beams etc.
beam.jpg

Comments

• Jul 5, 2017 - 18:46

- This nightly works (well, except some unexpected results for some lines, but no crash) : dd7fbe2
- Systematic crash (current result) with this one: 78d4ebe

At first sight, I do not see anything really obvious about spanners. (Edit: after further checking, possibly related to this "big" commit? ) : https://github.com/musescore/MuseScore/commit/be89a2de5e7594c632fedd032…

In other words, I would be curious to know if the whole edit mode will be changed or not for the 3.0?
Ie a simple click would be enough to edit everything you want? Or, if we put aside the text edition: in the case of lines and others spanners, edit mode with double-click will still be preserved?

Reply

• Jul 7, 2017 - 10:00

I would like to get rid of "editing mode" and make some operations simpler. Unfortunately this did not work out. Making one operation easier makes other operations more difficult.
Editing mode is now more lightweight. Every change in edit mode is now put on the undo/redo stack. In the old version all changes in edit mode could only be reverted in on step which interacts badly with inspector changes in between.

Reply

• Jul 7, 2017 - 10:16

Okay, useful information.
For now, this sentence " Every change in edit mode is now put on the undo/redo stack"
is too "abstract" (for me!)
But, in practice and in time, I will probably understand the changes made. Thanks.

Reply