Glissando goes through clef

2.0.2 / Win 10.

Same behavior in current version.

Do you have an implementation strategy in mind for this? Offhand, it seems like this would require a fairly major overhaul of the glissando class code and indeed the implementation of the class itself. Or is there some easier method I am not thinking of? If so, it would be nice to apply it also to ties.

I first thought it might be easier than that, but I can't find a way without making changes to the class too. Unassigned myself.

I don't necessarily think the current behavior is wrong. If there is a clef in the line of fire of a gliss, it is ineveitable they will intersect, even if you "place the new clef-mid-way through the glissando". And if was playing a chart that had the gliss according to your expected behavior ("the glissando stops before the clef and resumes after"), then I might not even think it is a gliss...I might equally be likely to think that the composer wants me to slide out up from the first note, and the basically skip a bunch of intermediatry notes, and the slide in up to the top note. Regardless, I'm going to be confused.

I think it would be preffereable for whoever is notating that section of music to simply not have a clef change inside a gliss. Clef changes are better at the start of a phrase (or if have to put in a phrase, preferrably at a more convenient point like after a longer note). In this example case, I personally would just prefer the person notating to use an 8va symbol above that high F.

Anyway, I don't think the case occurs often enough to warrent special changes in the code.

Another comment in Option for masking ties crossing key signatures .