bug-lilypond
[Top][All Lists]
Advanced

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

line-break-system-details and the exact vertical position


From: Robin Bannister
Subject: line-break-system-details and the exact vertical position
Date: Mon, 21 Mar 2022 12:38:48 +0100
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1

Hallo there

In the Notation Reference for v2.12 through to (currently) v2.23, the section 'Explicit staff and system positioning' says:
Note that line-break-system-details takes an associative list of potentially many values, but that we set only one value here. Note, too, that the Y-offset property here determines the exact vertical position on the page at which each new system will render.

That bit about 'determines the exact vertical position' was written during v2.11 and described v2.12 behaviour. But v2.13 started doing it differently, and that discrepancy between docs and code still exists.

I think the user thread
https://lists.gnu.org/archive/html/lilypond-user/2011-05/msg00332.html
can serve as a bug report for the current situation. It summarises the situation and provides MWEs and even includes a patch.

That patch wasn't applied, perhaps because Trevor Bača's particular problem was solved without resort to line-break-system-details.

I suppose it stayed that way because when moving a _single_ line you use trial and error to arrive at a suitable value. Or when aligning _two_ lines there are more familiar methods to fall back on, so any temporary inaccuracy or confusion becomes irrelevant (cf mirrored.png).

In
https://lists.gnu.org/archive/html/lilypond-user/2022-03/msg00224.html
pseudoIndentsYdemo.ly's apply-Y-pos uses line-break-system-details with a crude workaround. If you gradually reduce even-taller's value, the end of scoreA starts moving at 7 and scoreE bit later. I ought to be able to align the 3 fragments of line 4 in a clean LilyPond way.


Cheers,
Robin

Attachment: mirrored.png
Description: PNG image


reply via email to

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