Am 11.05.2018 um 11:25 schrieb Malte Meyn:
Am 11.05.2018 um 11:16 schrieb Malte Meyn:
I found a way to do this for scores but not for toplevel markups.
It’s not even a complicated calculation: just let
VerticalAxisGroup.after-line-breaking print it’s Y-extent.
Oops, forgot about scores with multiple staves … And I’d thought that
VerticalAxisGroup lived in Score.
I tried to print the Y-offset too but it seems like
ly:hara-kiri-group-spanner::force-hara-kiri-callback doesn’t only get
the offset but set it so asking for it
(ly:grob-property grob 'Y-extent)
has a side-effect: It shifts the next staff (see code below). I’ll
have a closer look and come back when I find something better.
OK, looking forward to it.
Am 11.05.2018 um 11:16 schrieb Malte Meyn:
Does this already help? I don’t know how much of this should be done
in LilyPond and Lua/LuaLaTeX …
I think so. What this should do in LilyPond is write the highest point
of the top-most staff and the lowest point of the lowest staff to a
file, e.g. <basename>.extent. The format is pretty much irrelevant, but
the best would probably be to simply have two numbers, i.e. this as the
single line in the file:
-3 4.23
referring to a file that spans -3 to 4.23 staff spaces around the middle
staffline.
Best
Urs
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
