|
From: | lilypond |
Subject: | Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes |
Date: | Mon, 21 Jan 2013 09:11:23 +0000 |
Comment #37 on issue 2990 by address@hidden: \RemoveEmptyStaves in StaffGroup context crashes
http://code.google.com/p/lilypond/issues/detail?id=2990Issue 3101 is not actually a "real fix". It just avoids the main condition under which we previously got multiple VerticalAxisGroup engravers. So it should definitely help against \RemoveEmptyStaves related crashes.
It won't help against people manually adding AxisGroupEngraver. The currently committed fix for _this_ issue apparently only catches a simple subset of those. I'd like a better fix than that: it would be nice if one could, say, nest a Staff inside of a Staff and such, and the main complication is killing the inner Axis_Group_Engraver before it causes havoc.
I think this may have worked in 2.16 times: the allergy against multiple Axis Groups is likely just from the skyline patch.
[Prev in Thread] | Current Thread | [Next in Thread] |