Glissando not seen in linked staff, crash with linked parts
1, Create standard guitar score with standard linked stave.
2. Enable 'Note Entry'.
3. Enter one note, then another next to it.
4. Disable 'Note Entry'.
5. Click on the first note of either stave.
6. Apply glissando.
Result: It does not appear in the other stave.
Using MuseScore 2.0 Nightly Build 75018ae - Mac 10.7.5.
Comments
The glissando appears but not the glissando text.
![text glissando.jpg]( "text glissando.jpg")
By default, the text is not displayed in the Tab staff.
The text probably should be mirrored, but that's not what I was reporting.
What build and OS are you using?
Using MuseScore 2.0 Nightly Build 201c75c - Mac 10.7.5.
You are right. And I can no longer replicate my own image of the previous comment #1(with standard + linked Tab staff), I do not know why. There is an issue indeed.
Incidentally, the following issue is probably by design: #16288: Glissando text doesn't appear for minims or lower values
Worse - they also don't show up in linked *parts*, and I got a crash trying.
1) new score, treble clef template
2) generate parts
3) first measure of score: add two half notes G & A
4) select the G
5) double click gliss in palette
Result: crash
It seems from the crash that the glissando is being created in the linked staff but not actually given any segments.
The problem is that, when the glissando is cloned into the other linked staff or part, its start element and end element are kept the same in the clone too, ignoring the fact that the clone belongs to a different staff / score.
I am rather sure I wrote code to deal with this, as I am also pretty sure that at least the case depicted in #1 was working in my original implementation.
Trying to understand what happened to it...
There have indeed been recent changes to calculation of start and/or end elements in some cases - well, end anyhow. But the ones I know of should not have affected simple cases like these.
If you see suspicious code with my name on it, please don't hesitate to ask. Here's one recent change I made that could be involved:
https://github.com/musescore/MuseScore/pull/1753/files
I do not have time right now to investigate further.
But the key is likely: the glissando does not appear in the linked staff, tab (for example), because it overlaps the glissando of the first standard staff.
The phenomen may be seen by moving the glissando in the first staff. See also the anchor may be different if glissando with straight or wavy lines? And if you enter notes in the standard or TAB staff?
Produced with this Nightly on February 18: ff962d5
![result1.jpg]( "result1.jpg")
![result2.jpg]( "result2.jpg")
And reproducible with this one: 6b554a9
PR pushed to github: https://github.com/musescore/MuseScore/pull/1821
Fixed in 65973bb245
Automatically closed -- issue fixed for 2 weeks with no activity.