Slurs not correctly continuing over multiple system breaks

• Dec 4, 2018 - 05:58
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project
MuseScore

Applying a slur that goes over multiple staff breaks results in them only showing for the first measure. See the blue highlighted slur in the attached photos for the offending culprits. It seems as though if the slur extends beyond two breaks, only the previous line is affected.

Attachment Size
Slur problem.png 79.41 KB
Slur problem 2.png 37.53 KB

Comments

• Dec 4, 2018 - 08:32
Title Slurs not correctly continuing over multiple systembreaks ⇒ Slurs not correctly continuing over multiple system breaks
Regression No ⇒ Yes
Severity S4 - Minor ⇒ S3 - Major
Priority ⇒ P1 - High

Confirmed, sluring to 1st chord/rest in 3rd system creates a to short slur in 2nd system. Sluring to 2nd chordrest in 3rd system fixes it again, extending to 1st chord/rest in 4th system and it breaks in 3rd system.

While playing with it, MuseScore crashed on me...

Reply

• Dec 6, 2018 - 09:02

I get a crash too, like this:
1) Enter a note and add slur
2) Extend slur with Shift + right arrow
3) Just when the slur extended to the second system - image below -, leave Shift, and press only Right arrow

---> Crash
here.jpg

Reply

• Dec 6, 2018 - 09:08
Severity S3 - Major ⇒ S2 - Critical

Oups... sorry, not seen the priority change and the Critical PO before my comment.

EDIT : and the change appears on January 5, 2017

Here, it works as expected: 0b1aea9

With this one, issue and crash: 73a2e6a

Reply

• Dec 8, 2018 - 09:30

Yes, that is exactly what @Jojo-Schmitz told about. The problem reveals if a slur ends on the first note of the system, and my PR fixes that.

Reply

• Dec 10, 2018 - 10:32
Status PR created ⇒ fixed

Fixed in branch master, commit 2fbbf5cdfc

fix #279340: crash and incorrect middle segment length of slurs

Changes:
1) Reinitialize edit mode when changing the edited element.
Fixes a crash on dragging slur after increasing its size to more
than one system.
2) Correct segment type determination for slur segments.
For slurs tick2 is at the beginning of the end point unlike as
for most of other spanners.
3) Be more cautious on resetting spanner segment parent on system
destruction. No known issues related to this.

Reply