Hi David,
thank you for looking into it. Unfortunately I don't really see how that works
from the diff.
Does David's comment suggest that it would be possible to keep track of the
barnumber difference through a Scheme engraver? Or is this some information
that already gets lost in the C++ code, so it would require an update to
LilyPond itself?
Urs
3. Oktober 2019 21:07, "Davide Liessi" <davide.lie...@gmail.com> schrieb:
> What about introducing a new grob property containing the _printed_
> bar number and the measure position?
> Unless, of course, there is already a way to retrieve the desired information.
>
> With the attached patch, the input file
>
> \version "2.19.82"
> {
> \override Score.BarNumber.break-visibility = ##(#t #t #t)
> \override NoteHead.after-line-breaking =
> #(lambda (grob)
> (ly:message "Internal location: ~a" (grob::rhythmic-location grob))
> (ly:message "Printed location: ~a" (grob::printed-rhythmic-location grob)))
> c'1
> \set Score.currentBarNumber = 12
> c'1
> }
>
> has the following output:
>
> [...]
> Internal location: (1 . #<Mom 0>)
> Printed location: (1 . #<Mom 0>)
> Internal location: (2 . #<Mom 0>)
> Printed location: (12 . #<Mom 0>)
> [...]
>
> Best wishes.
> Davide
>
> _______________________________________________
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
