On Nov 1, 2013, at 8:31 AM, lemzw...@googlemail.com wrote:
>
> https://codereview.appspot.com/18090043/diff/60001/lily/axis-group-interface.cc
> File lily/axis-group-interface.cc (right):
>
> https://codereview.appspot.com/18090043/diff/60001/lily/axis-group-interface.cc#newcode507
> lily/axis-
https://codereview.appspot.com/18090043/diff/60001/lily/axis-group-interface.cc
File lily/axis-group-interface.cc (right):
https://codereview.appspot.com/18090043/diff/60001/lily/axis-group-interface.cc#newcode507
lily/axis-group-interface.cc:507: should probably not check for suidided
items or
On Nov 1, 2013, at 7:49 AM, k-ohara5...@oco.net wrote:
> On 2013/10/30 08:09:53, mike7 wrote:
>> On Oct 30, 2013, at 8:32 AM, mailto:k-ohara5...@oco.net wrote:
>
>> > I do not understand the Todo: comment; nothing should have been
> suicided
>> > at this stage.
>
>> The original clef is suicide
On 2013/10/30 08:09:53, mike7 wrote:
On Oct 30, 2013, at 8:32 AM, mailto:k-ohara5...@oco.net wrote:
> I do not understand the Todo: comment; nothing should have been
suicided
> at this stage.
The original clef is suicided in the handle_prebroken_dependencies
function,
which is the same
On Oct 30, 2013, at 8:32 AM, k-ohara5...@oco.net wrote:
> I do not understand the Todo: comment; nothing should have been suicided
> at this stage. What is the life cycle of a Clef and the copies made for
> line-breaking possibilities?
The original clef is suicided in the handle_prebroken_depend
This looks correct.
It includes a pointer to the potential Clef in every single measure in
'pure-relevant-grobs', but the user of that list checks whether the Clef
would be visible.
The output with annotate-spacing=##t looks correct. The bar numbers are
still tentatively placed against the top
