On 4/14/09 4:20 PM, "Neil Puttock" wrote:
> 2009/4/14 Carl D. Sorensen :
>
>> It seems to me to be the same to set an alist for AutoBeamSetting. When
>> it's time to do the auto-beam calculations, the code can ask the context for
>> the property setting.
>
> Fine, but you can't make it appe
2009/4/14 Carl D. Sorensen :
> It seems to me to be the same to set an alist for AutoBeamSetting. When
> it's time to do the auto-beam calculations, the code can ask the context for
> the property setting.
Fine, but you can't make it appear to be a grob; it must be
autoBeamSetting as a context p
On 4/14/09 2:19 PM, "Neil Puttock" wrote:
> 2009/4/14 Carl D. Sorensen :
>>
>>
>>
>> On 4/14/09 1:39 AM, "Mats Bengtsson" wrote:
>>
>>> Have you forgot about the most basic difference between a context
>>> property and a grob property?
>>> All grob property are connected to a specific gra
On 4/14/09 2:19 PM, "Neil Puttock" wrote:
> 2009/4/14 Carl D. Sorensen :
>>
>>
>>
>> On 4/14/09 1:39 AM, "Mats Bengtsson" wrote:
>>
>>> Have you forgot about the most basic difference between a context
>>> property and a grob property?
>>> All grob property are connected to a specific gra
2009/4/14 Carl D. Sorensen :
>
>
>
> On 4/14/09 1:39 AM, "Mats Bengtsson" wrote:
>
>> Have you forgot about the most basic difference between a context
>> property and a grob property?
>> All grob property are connected to a specific graphical object, so the
>> syntax is
>> \override Object #'prop
Carl D. Sorensen wrote Tuesday, April 14, 2009 7:37 PM
On 4/14/09 1:39 AM, "Mats Bengtsson"
wrote:
Have you forgot about the most basic difference between a context
property and a grob property?
All grob property are connected to a specific graphical object,
so the
syntax is
\override Obj
On 4/14/09 1:39 AM, "Mats Bengtsson" wrote:
> Have you forgot about the most basic difference between a context
> property and a grob property?
> All grob property are connected to a specific graphical object, so the
> syntax is
> \override Object #'propertyname = ...
> In this case, there is
Hi all,
a few days ago I asked this on the -user list and got no response:
If a melisma occurs on a word's last syllable, I want lilypond to
calculate the length of the melisma and automatically decide, whether an
extender line is appropriate or not. The user should be able to enter a
value for
Mats
I guess this was addressed to Carl, as that's
exactly what I said.
Trevor
- Original Message -
From: "Mats Bengtsson"
To: "Trevor Daniels"
Cc: "Carl D. Sorensen" ; "Lily-Devel List"
Sent: Tuesday, April 14, 2009 8:39 AM
Subject: Re: Reverting Beat Grouping Commands
Have yo
Have you forgot about the most basic difference between a context
property and a grob property?
All grob property are connected to a specific graphical object, so the
syntax is
\override Object #'propertyname = ...
In this case, there is no graphical object involved, right? Therefore,
it's natu
2009/4/14 Trevor Daniels :
> Hi Francisco
>
> You're right - these terms are better not indexed, so they can be
> translated.
>
> Trevor
Then I'll remove them.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org
___
lilypond-devel mailing list
lilypon
Carl D. Sorensen wrote Monday, April 13, 2009 5:53 PM
On 4/13/09 10:49 AM, "Graham Percival"
wrote:
Speaking strictly from a user's point of view, why not keep the
\set beatGrouping = #'(3 3 2)
which automatically takes the denominator of the time signature?
ok, from a code standpoint you
Carl D. Sorensen wrote Monday, April 13, 2009 1:59 PM
On 4/13/09 2:44 AM, "Trevor Daniels"
wrote:
Should this not be \set rather than \override, as
this is a context property?
According to LM 5.3.5, autoBeamSetting would not be a context
property,
because it doesn't change over time. (I
Hi Francisco
You're right - these terms are better not indexed, so they can be
translated.
Trevor
- Original Message -
From: "Francisco Vila"
To:
Sent: Monday, April 13, 2009 11:20 PM
Subject: funindexed words
Hello, while updating the translation of rhythms.itely I've found
so
14 matches
Mail list logo
