lilypond-devel
[Top][All Lists]
Advanced

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

Re: convert-ly rule


From: address@hidden
Subject: Re: convert-ly rule
Date: Wed, 13 Mar 2013 11:21:33 +0100

On 13 mars 2013, at 10:51, David Kastrup <address@hidden> wrote:

> "address@hidden" <address@hidden> writes:
> 
>> Hey all,
>> 
>> I'm not too good at writing convert-ly rules.  Is there a model I can
>> use for replacing a property with another?  Specifically, I'd like to
>> write a patch changing:
>> 
>> TupletBracket.staff-padding
>> 
>> to:
>> 
>> TupletBracket.bracket-staff-padding
>> 
>> as one cannot currently use the side position interface callbacks on
>> TupletBrackets because staff-padding in the tuplet-bracket-interface
>> works differently than staff-padding in the side-position-interface.
> 
> Is bracket-staff-padding a smart name?  We also have OttavaBracket,
> VoltaBracket, PianoPedalBracket, ArpeggioBracket, BassFigureBracket,
> LigatureBracket, HorizontalBracket, SystemStartBracket...  This sounds
> like a recipe for the next naming collision.
> 
> Maybe tuplet-staff-padding instead?  What is it being used for?
> 

It's being used for ligature bracket and tuplet bracket.

I don't mind tuplet-bracket-staff-padding, but that is counterintuitive for 
ligature brackets...

Cheers,
MS
> 
> 
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-devel



reply via email to

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