Glissando not copied if destination staff has links
Reported version
3.0
Type
Functional
Frequency
Many
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
- Create a score with two linked staves and enter two notes and glissando in first measure
- Note that the glissando is also present in the link staff
- Copy paste the first measure of the first staff to the second measure
Expected result: the glissando is copied in measure 2 in both staves
Actual result: the glissando is copied only in the top staff.
Quick investigation: The Note copy constructor is probably incomplete and needs to take care of spannerFor and spannerBack (?)
| Attachment | Size |
|---|---|
| glisstest.mscz | 9.06 KB |
Fix version
3.1.0
Comments
PR pushed to github: https://github.com/musescore/MuseScore/pull/1862
Fixed in bb8026f25a
Automatically closed -- issue fixed for 2 weeks with no activity.
Since the fix was quite "partial" - gliss is not copied at all if destination has links - I'm re-opening this. Same steps to reproduce as in the original, but the result after the partial fix is that the glissando is not copied at all.
(This came up again in https://musescore.org/en/node/66326)
Came up again: #165616: Glissando does not copy in 2.1-dev and 2.0.3
In reply to #6 by cadiz1
One more in: https://musescore.org/en/node/271671
Came up in https://musescore.org/en/node/274288
Came up again (the most likely related) in #287358: Glissandos don't paste correctly if a score has parts.
Now that we have a mechanism for making this possible, the only thing now preventing the pasting of glissandos into linked staves is the code that was added to specifically disallow it. Remove that code, and it works as it should. See https://github.com/musescore/MuseScore/pull/5031
Fixed in branch master, commit 282a443141
fix #49856: Glissando not copied if destination staff has links
Fixed in branch master, commit aa81f8d979
_Merge pull request #5031 from mattmcclinch/49856-paste-glissando
fix #49856: Glissando not copied if destination staff has links_
Automatically closed -- issue fixed for 2 weeks with no activity.