[Top][All Lists]

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

Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-co

From: lilypond
Subject: Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly
Date: Mon, 24 May 2010 21:19:41 +0000

Comment #9 on issue 1031 by pnorcks: constantly-changing input/regression/rest-collision-beam-note.ly

(Ignore my last comment.)

There are certain cases where pointer addresses are compared in staff_priority_less. If I comment out these two lines of code, the problem seems to be fixed, though I
haven't run `make check' to verify.

/* if neither grob has an outside-staff priority, the ordering will have no
     effect -- we just need to choose a consistent ordering. We do this to
     avoid the side-effect of calculating extents. */
  if (isinf (priority_1))
    return g1 < g2;

Is this the likely cause of the inconsistency?

reply via email to

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