On 12/15/10 3:43 PM, "Neil Puttock" <[email protected]> wrote:
> On 10 August 2010 01:08, Carl Sorensen <[email protected]> wrote:
>> On 8/9/10 5:22 PM, "Trevor Daniels" <[email protected]> wrote:
>>>
>>>
>>> Neil Puttock wrote Monday, August 09, 2010 9:07 PM
>>>
>>>
>>>> On 6 August 2010 20:36, Trevor Daniels <[email protected]>
>>>> wrote:
>>>>
>>>>> Second, this only seems to work in the Score context.
>>>>> I don't know if this is a bug or an error in the
>>>>> documentation. We'll have to wait for Carl to return
>>>>> from vacation to check this out.
>>>>
>>>> It is a bug, but one which I think will prove intractable for
>>>> timeSignatureSettings, since the context inside \time is
>>>> hard-coded
>>>> (to the Timing alias): it only reads timeSignatureSettings at the
>>>> Score level unless the Timing_translator's moved.
>>>
>>> Looks like the solution is a doc change to make this clear, then.
>>
>> Or perhaps we should change the context inside \time. I'll try to have a
>> look at this this week.
>
> Carl, have you had time to investigate fixing this yet?
I think the solution is a documentation change. timeSignatureSettings can
only apply to the context containing the time signature, i.e. wherever the
Timing_translator is.
If we want to have beam settings set by the timeSignatureSettings property,
and we want different time signatures in different staves, we will need to
move the Timing_translator to the Staff context, instead of the Score
context.
I'll cook a patch to the documentation.
Thanks,
Carl
_______________________________________________
lilypond-user mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-user
