lilypond-auto
[Top][All Lists]
Advanced

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

Re: [Lilypond-auto] Issue 3359 in lilypond: ties for notes in \changed S


From: lilypond
Subject: Re: [Lilypond-auto] Issue 3359 in lilypond: ties for notes in \changed Staff brings LP to crash
Date: Sat, 18 May 2013 22:10:28 +0000

Updates:
        Labels: Regression

Comment #10 on issue 3359 by address@hidden: ties for notes in \changed Staff brings LP to crash
http://code.google.com/p/lilypond/issues/detail?id=3359

The patch for issue 542 skipped over a null pointer, but this problem does not involve null pointers.

After the patch for issue 3199, the Tie is on the list of 'pure-relevant-grobs' for the Staff that is not its parent. This causes the 'pure-Y-common' for the Staff to be the overall VerticalAlignment (the common (grand)parent of Tie and Staff). Then the initial page-layout asks the Staff for its 'pure-height', the Staff tries to answer in terms of its position relative to the whole system, requiring page-layout, and we have an endless recursion until the stack crashes.

Either the Tie is not 'pure-relvant' to the Staff, or 'pure-Y-common' should refrain from pointing to objects outside its own Staff (more generally VerticalAxisGroup) ... or maybe we define a pure-translation as an initial guess for a Staff position in the system, and then 'pure-pure-height' to estimate positions without triggering calculations of 'pure-translation' ...

Note that released builds give .pdf output showing the rest of the score with just the Tie misplaced, and debug builds give a reasonably-helpful message.

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings



reply via email to

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