Re: Spanning MetronomeMark

2025-01-02 Thread Thomas Morley
Am Do., 2. Jan. 2025 um 21:36 Uhr schrieb Saul Tobin : > > Would this MR potentially also fix > https://gitlab.com/lilypond/lilypond/-/issues/6640 and > https://gitlab.com/lilypond/lilypond/-/issues/6641? Well, it _can't_ fix those issues, because it proposes a different grob. Maybe you can use

Re: Spanning MetronomeMark

2025-01-02 Thread Saul Tobin
Would this MR potentially also fix https://gitlab.com/lilypond/lilypond/-/issues/6640 and https://gitlab.com/lilypond/lilypond/-/issues/6641? On Thu, Jan 2, 2025 at 3:21 PM Simon Albrecht wrote: > On 30.12.24 16:04, Thomas Morley wrote: > > There's alsohttps://gitlab.com/lilypond/lilypond/-/merg

Re: Spanning MetronomeMark

2025-01-02 Thread Simon Albrecht
On 30.12.24 16:04, Thomas Morley wrote: There's alsohttps://gitlab.com/lilypond/lilypond/-/merge_requests/2256 with a serious drawback. CC’ing devel list now. This would be a really important improvement IMO. Do we have no one to advise with this cyclic dependency issue? :( Best, Simon