Slur should be deleted when changing duration of note deletes subsequent notes connected to the slur.

• Jan 2, 2019 - 15:05
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project
MuseScore
  1. open change-note-duation-slur-fail.mscz
  2. click first note
  3. select duration whole note

Result: One slur is completely orphaned cause it lost chords for the first and last pitch, and so should be deleted. The other slur is still connected to the first note only, although I still think it should be deleted, because most likely user doesn't want to leave a partially connected slur:

slurs-should-be-deleted-bug.gif

MuseScore 2.3.2 deletes both slurs, which is what I think should happen, so I'm marking this as a regression.

I'm on MuseScore 3.0 release.

Comments

• Jan 4, 2019 - 14:54

@jojo, apparently the loading of the score cleaned those slurs out. I did indeed save the file with the slurs (exactly as the beginning of the gif image looks), and the score's thumbnail does have slurs (if you look at the file when loading), however upon actual load and first update, the slurs are deleted.

Might be some sanitization process happening during save or load or first update... But indeed it is possible to create these orphaned slurs.

Mabye because I did a Ctrl->undo of the orphaned slurs before saving...maybe that caused the slurs to be in a simultaneously state of not existing and existing.

Reply

• Apr 4, 2019 - 11:14

Fixed in branch master, commit a01cf31bf4

_Merge pull request #4855 from dmitrio95/45361-copy-paste-replace-elements

fix #45361, fix #281083: remove extra annotations and spanners on paste and note duration change_

Reply

Fix version
3.1.0