lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Planning for 2.22.2


From: Jonas Hahnfeld
Subject: Re: Planning for 2.22.2
Date: Mon, 10 Jan 2022 22:22:14 +0100
User-agent: Evolution 3.42.3

Am Montag, dem 10.01.2022 um 21:43 +0100 schrieb Jean Abou Samra:
> Le 10/01/2022 à 20:35, Jonas Hahnfeld via Discussions on LilyPond 
> development a écrit :
> > I would have liked to include some more balloon fixes, but already
> > https://gitlab.com/lilypond/lilypond/-/merge_requests/1071 doesn't
> > produce the expected results (no footnote on the MultiMeasureRestNumber
> > and \after is not available in 2.22 at all),
> 
> 
> Right, I didn't realize that. I think it's a case
> fixed by
> 
> commit 4f474c99d1f7afdec28a159bf1ccc99d619c7dc7
> Author: Jean Abou Samra <jean@abou-samra.fr>
> Date:   Mon Sep 20 21:11:37 2021 +0200
> 
>      Let get_bound default to host's bound for sticky spanners

But we don't have sticky spanners in stable/2.22, do we?

> Also, !1071 is likely not to fix an actual problem if you
> don't backport
> 
> commit ac703cc5b7d8c54650ac36677243799bf2772169
> Author: Jean Abou Samra <jean@abou-samra.fr>
> Date:   Tue Sep 21 00:39:57 2021 +0200
> 
>      Set X parent of sticky spanner to host

Same here.

> > and the fix from
> > https://gitlab.com/lilypond/lilypond/-/merge_requests/1077 doesn't seem
> > to work either.
> 
> It will fix footnotes, but not balloons because you'd
> most likely also need
> 
> commit 10e8952de0494a65323e9d9b2ecef129c7f7f8ca
> Author: Jean Abou Samra <jean@abou-samra.fr>
> Date:   Sat May 22 11:36:47 2021 +0200
> 
>      Fix balloons on grobs with empty pure Y extent
> 
> [...]
> 
> Wait, actually I see it in the stable/2.22 branch,
> and if I backport d22f1bb88e manually, it seems
> to work. Not sure how you've tested it?

Yes, the balloon on the beam seems to "work". The one on the
LedgerLineSpanner doesn't, as expected for that commit. Note that this
was before the whole sticky spanner business.

> At any rate, even if the spacing differences that
> d22f1bb88e causes for glissandi where the Y endpoints have been
> overridden explicitly are good-natured, they're a bit
> more than we'd want to put in a point release I think.

Hm, my repository doesn't know about that commit hash. Is that your
local cherry-pick of

commit 098c808206a304d227d0aacc311f0c3dfac603d3
Author: Jean Abou Samra <jean@abou-samra.fr>
Date:   Fri Dec 24 09:00:30 2021 +0100

    Don't set empty extents for Glissando and VoiceFollower

?

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]