Re: Autobeaming

[Carl Sorensen]

On 12/29/09 1:40 AM, "David Kastrup" <address@hidden> wrote:

> Carl Sorensen <address@hidden> writes:
> 
>> Then, if desired, the user can change the values of beatLength,
>> measureGrouping, or autoBeamRules, they can do so directly by means of
>> the \set command.
>> 
>> If a user wants to change the timeSignatureSettings values for beatLength,
>> measureGrouping, or autoBeamRules, they can do so with an
>> \overrideTimeSignatureSettings or \revertTimeSignatureSettings command.
>> Having done so, a simple change of time signature will implement the new
>> time signature settings.
>> 
>> Does this seem like a feasible architecture?
> 
> I don't like compound contraptions like \overrideTimeSignatureSettings.
> Can't this be made to work with \override timeSignatureSettings (or
> similar) in some manner?

I don't like them either.  But I haven't been able to figure out another way
to do it.

\override requires a grob; timeSignatureSettings is a context property, not
a grob description, so it won't work with \override.

I went through some attempts earlier to try to make \override work, but
wasn't successful.

http://thread.gmane.org/gmane.comp.gnu.lilypond.devel/21942/
http://thread.gmane.org/gmane.comp.gnu.lilypond.devel/20632/
http://thread.gmane.org/gmane.comp.gnu.lilypond.general/41837/focus=20624

If you can figure out how to make it work with \override, I'd be delighted.

But this gets back to your initial question (which probably never got
answered to your satisfaction) as to the difference between context
properties and grob descriptions.

So, since I couldn't figure out a way to make it work, I did a workaround.

Thanks,

Carl