Crash when changing glissando properties in Inspector
1. Open attached score (produced in 1.3).
2. 'View'>'Inspector'.
3. Click on glissando.
4. Change anything in the Glissando section of the Inspector (e.g. tick 'Show Text')
Result: Crash.
Notes:
See attached log.
It is also reproducible in a 2.0 score with a similar description (e.g. 32 bar voice score with the same notes).
Using MuseScore 2.0 Nightly Build 561cae3 - Mac 10.7.5.
(Thanks to Dangthrimble .)
Attachment | Size |
---|---|
Crash when changing glissando properties in Inspector.mscz | 1.54 KB |
Crash when changing glissando properties in Inspector [Log].txt | 55.5 KB |
Comments
Crash is due to the GLISS_SHOW_TEXT property not being handled by GlissandoSegment, which is what is actually selected (as opposed to Glissando, which does handle it). Ditto with GLISS_TYPE. Works just fine if the Glissando is selected rather than the GlissandoSegment, and apparently that happens sometimes. Not sure why; might have to do with whether the gliss is short enough that the text is suppressed.
PR pushed to github: https://github.com/musescore/MuseScore/pull/1820
Travis is going crazy, though; not sure how long it will take for current PR's to be merged.
In fact, I'm about to withdraw the patch.
There is an easier cheap fix, routing properties of the whole Glissando from the GlissandoSegment which got select by chance to its 'parent' Glissando.
But in fact, several points of the Inspector for spanners are questionable. Through the Inspector, one never knows -- at least I never know -- if one is managing the whole spanner or one its segment(s) and this applies to several (most? all?) types of spanner. Probably is too late for a general fix, but the matter should be reconsidered soonish.
New improved PR pushed to github: https://github.com/musescore/MuseScore/pull/1822
It should also fix #49141: Glissando not always drawn after dragging it, which has a lot in common with this issue. Possibly, it also fixes or at least improves other glissando issues, stemming from selection glitches.
Fixed in b12132258d
Automatically closed -- issue fixed for 2 weeks with no activity.