lilypond-devel
[Top][All Lists]
Advanced

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

Re: Reverting Beat Grouping Commands


From: Carl D. Sorensen
Subject: Re: Reverting Beat Grouping Commands
Date: Sat, 25 Apr 2009 11:24:33 -0600

Resending including lily-devel.  Sorry, Neil, for the noise.


On 4/25/09 9:27 AM, "Neil Puttock" <address@hidden> wrote:

> 2009/4/25 Carl D. Sorensen <address@hidden>:
>> 
>> 
>> 
>> On 4/25/09 8:24 AM, "Neil Puttock" <address@hidden> wrote:
>> 
>>> 2009/4/22 Carl D. Sorensen <address@hidden>:
>>> 
>>>> Does this help clarify what I'm thinking?
>>> 
>>> Yes, thank you.
>>> 
>>> To be honest, I'm not convinced by the idea of using a fake grob just
>>> for the convenience of easy overriding and reverting.
>> 
>> Why would we not want to develop a mechanism that allows the use of standard
>> LilyPond syntax?
> 
> It's not standard syntax for context properties to pretend to be a
> non-existent grob purely for the purposes of using \override and
> \revert.
> 
>> What are the disadvantages you see to this method?
> 
> None from a practical perspective.
> 
> I just think all-grob-descriptions should be reserved for real grobs.

OK, then, can we define a new context property called, e.g.
RevertibleContextProperties, and then call

\override RevertibleContextProperties #'auto-beam-settings #'(end 2 2) =
my-new-autobeam setting

Then, instead of defining a grob property, we could just, as part of
engraver-init.ly, set RevertibleContextProperties = '().

Does this seem better?

Carl





reply via email to

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