Select all glissandos in Range Selection fails
Reported version
3.0
Type
Graphical (UI)
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
1. Create any score with several glissandos
2. Select a range of notes that contains more than 1 glissando
3. Right click a glissando and click Select->All similar elements in range selection
Results: nothing is selected
Select->all similar elements and ->all similar elements in staff select the correct glissandos
Fix version
3.1.0
Comments
I just selected a measure that contained a glissando from the first note to the second note. My select included all but the chord symbols. I then tried to paste that measure onto a measure that contain the first note, which ended both a slur and a tie, and rests. Everything expected pasted except the glissando.
Further testing seems to indicate that the paste works if pasted into an untouched measure, but not even into a measure that has been erased.
The copy fails, because the select fails already.
In reply to The copy fails, because the… by Jojo-Schmitz
I don't understand your reply. If the select or the copy failed, then I wouldn't be able to paste into an untouched measure. However, after selecting a measure with a glissando and copying (^C), I have successfully pasted (^V) multiple times into untouched measures but been unable to paste everything into modified measures, including measures with nothing left but rests.
Bug still present in MSc3 . Context menu Select/more also not functional.
Windows 10 (10.0) (64-bit): 3.0.5.5992, -58dd23d
"Also in the 32-bit version.
It looks defective even in the Nightly d4b829c" as confirmed in
https://musescore.org/en/node/289496
See https://github.com/musescore/MuseScore/pull/5052.
Fixed in branch master, commit cd2d460907
fix #179251: Select all glissandos in Range Selection fails
Fixed in branch master, commit cd2979070f
_Merge pull request #5052 from mattmcclinch/179251-select-glissandos
fix #179251: Select all glissandos in Range Selection fails_
Automatically closed -- issue fixed for 2 weeks with no activity.