Dear David,

this sounds great! Thank you very much!
But first of all: All the best for the current holidays!
I'll try this patch on tuesday when family-business is finished ;-)

Merry Christmas - or whatever holiday you are celebrating - to anybody, who is 
reading this :-)

Jan-Peter

Am 24. Dezember 2016 18:45:21 MEZ, schrieb David Nalesnik 
<david.nales...@gmail.com>:
>Hi,
>
>On Fri, Dec 23, 2016 at 11:01 AM, David Nalesnik
><david.nales...@gmail.com> wrote:
>
>>
>> The default is actually to allow the components of the church rest to
>> expand to fill the available space within the measure.  The symbols
>> making up the rest are assigned a padding value proportional to the
>> visual size of the measure.
>>
>> I think what you're after is some means to limit this expansion. 
>I've
>> attached a patch which creates a property ("no-stretch") which keeps
>> internal padding at its minimum value -- 1 staff space.  Note also
>the
>> test file.  I haven't tested it beyond what you see there.
>>
>> It might be nice to allow a maximum padding.  (I find 1.0 for padding
>> a little close.)  That would be easily done.
>>
>> Sorry that this is a patch you need to apply.  Putting this in Scheme
>> would require extensive recoding.
>>
>
>The following patch may be more sensible.
>
>It creates a new property, "church-rest-inner-padding," which when set
>controls the space between the symbols making up the rest.  This space
>is fixed.
>
>If the property is left unset, we get the current default behavior:
>the rest is spread out to fill the available space.
>
>If the "no spread" behavior" is desired as a default, we'd just need
>to add an entry for church-rest-inner-padding to scm/define-grobs.scm.
>To get the spreading back, you'd override to '().
>
>HTH,
>David
>
>P. S.  This patch is to current master, not to the patch in my earlier
>email.

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to