Slurs on the TAB Staff moves upward when inserting multiple measures
Reported version
3.3
Type
Development
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project
OS: macOS High Sierra (10.13)
Arch.: x86_64, MuseScore version (64-bit): 3.6.0.485472625
revision: 269baf7
Step to Reproduce:
1.Create Guitar Score (Guitar + Tablature)
2.Make some music with slurs
3.Insert multiple measures via add -> Measures -> Insert Measures…
or just type shortcut key, shirt+i 2 times
Result:
Slurs on the TAB Staff moves upward
*It happens where after selected measures.
Fix version
3.6.1
Comments
Please add a sample score, best before the insertion of those additional measures
In reply to Please add a sample score,… by Jojo-Schmitz
ok.
(edited, see other comment below)
In reply to You got the same result … by cadiz1
oh, really !
Good to know, even in v2.3.2...
workaround: Insert multiple single meaures
In reply to oh, really ! Good to know,… by kazuma yamamoto
"oh, really !
Good to know, even in v2.3.2..."
oops... no, sorry, I mixed my brushes with different versions on my desktop! :(
? No an issue in 2.3.2 and 3.5.2 anymore?
No issue in version 2 (2.3.2), issue with 3.5.2 (at least, right now)
In reply to No issue in version 2 (2.3… by cadiz1
yep, I also checked in v2.3.2.
It works fine.
This issue occurs on November 1, 2019
Regression from 3.3.1
Works with this commit (October 30): 438ab6b
And not five commits further with this one (so the most likely the origin of this issue): 9c5ee8e
To fix: #295703: Slurs to grace notes disappear after inserting measures
In reply to This issue occurs on… by cadiz1
Wow.. you found the spot.
Thank you very much, hope it will be fixed soon!
"Wow.. you found the spot."
As always, why ?!
Or very often ;)
"hope it will be fixed soon!"
I don't know.
I figured at first this would be a layout glitch that fixed itself on relayout or reload, but no, it's worse, the tab slur is getting attached to the standard staff somehow. The code added in the commit referenced above is trying to hand;e linked staves somehow, but I don't really follow it, and anyhow, it doesn't work in this case.
See https://github.com/musescore/MuseScore/pull/7344.
Fixed in branch 3.x, commit d9cf79ac59
_Fix #316137: Slurs on the TAB Staff move upward when inserting multiple measures
Resolves: https://musescore.org/en/node/316137.
In #5432, Score::undoChangeSpannerElements() was modified to allow for changing one or both of the elements to or from nullptr. However, in the case of a linked spanner, where we have to look for parallel elements in another track, we cannot use the track of the old spanner elements if they are null. A default track of 0 was arbitrarily chosen in this case, but that causes the spanner to be attached to the wrong staff. Fortunately, we can use the spanner's track() and track2() functions even if its elements are null._
Fixed in branch 3.6.1, commit 6b1932b203
_Fix #316137: Slurs on the TAB Staff move upward when inserting multiple measures
Resolves: https://musescore.org/en/node/316137.
In #5432, Score::undoChangeSpannerElements() was modified to allow for changing one or both of the elements to or from nullptr. However, in the case of a linked spanner, where we have to look for parallel elements in another track, we cannot use the track of the old spanner elements if they are null. A default track of 0 was arbitrarily chosen in this case, but that causes the spanner to be attached to the wrong staff. Fortunately, we can use the spanner's track() and track2() functions even if its elements are null._
Automatically closed -- issue fixed for 2 weeks with no activity.