Re: How to delete a created Glissando without impact on line break?
Thomas Morley <[email protected]> Sun, 28 Jun 2026 14:33:46 +0200
| Newsgroups | gmane.comp.gnu.lilypond.devel |
|---|---|
| Message-ID | <CABsfGyVKv1CNysNA3bzEkR+CvSbf_t6aiHsp=igP3KK=Ac2GKA@mail.gmail.com> |
Am So., 28. Juni 2026 um 14:12 Uhr schrieb Dan Eble <[email protected]>: > > On 2026-06-28 07:43, Thomas Morley wrote: > > Hi, > > > > The problem seems to be: once a Glissando-grob is created, it can't be > > suicided without causing linebreak issues. > > Weird things happen when downstream code uses dead grobs as if they were > live. How to prevent this? > > I would try making experimental changes to narrow down the possibilities. > > For example, Glissando has an interface called > unbreakable-spanner-interface. I would try removing that interface from > the definition and see what happens in your test case. Removing said interface from the Glissando grob-definition leads to normal breaks. Same if I use \override Glissando.breakable = ##t > If the line breaks normally, I would look into Spanner_break_forbid_engraver. Well, my C++ is near zero. Thus, looking into Spanner_break_forbid_engraver is not promising, even if I would understand I'm not able to make changes there. To fix #6946 it would be sufficient to create only those Glissando grobs really needed, then there would be no need to delete some of them afterwards. There seem to be some conditions for that purpose in the original cc-engraver, but I don't understand them sufficiently. > -- > Dan > > Thanks, Harm