On Apr 10, 2017, at 08:43, David Nalesnik <david.nales...@gmail.com> wrote: > > It's strange -- it seems that the value of > ly:tuplet-bracket::calc-x-offset is used sometimes regardless of the > ly:grob-set-property! and there's no predictability to it. > > No idea :(
Maybe there’s a race against the garbage collector. Did any recent changes to the C++ add SCM things but overlook handling the reference count? Does the behavior change if you force garbage collection (scm_gc()?) at key times in the course of engraving? say, right before calling the callback that has been behaving inconsistently? — Dan _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
