[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1299 in lilypond: ly/gregorian.ly needs minimum-Y-extent updat
From: |
Keith E OHara |
Subject: |
Re: Issue 1299 in lilypond: ly/gregorian.ly needs minimum-Y-extent updated |
Date: |
Wed, 17 Nov 2010 21:34:22 -0800 |
User-agent: |
Opera Mail/10.63 (Win32) |
On Wed, 17 Nov 2010 20:39:32 -0800, <address@hidden> wrote:
Updates:
Blockedon: 1298
Comment #2 on issue 1299 by percival.music.ca: ly/gregorian.ly needs
minimum-Y-extent updated
http://code.google.com/p/lilypond/issues/detail?id=1299
This item is waiting until there's clarification of issue 1298.
Graham,
From my point of view, Joe's last note on 1298 makes everything sufficiently
clear to proceed :
minimum-Y-extent is still a valid property of every grob,
and VerticalAxisGroup does support the grob-interface (*1),
*but*
the Y-extent of VerticalAxisGroups is no longer used to determine the spacing
of staves, so this particular use of minimum-Y-extent should be removed or
replaced from manual/web examples.
The convert-ly pattern that flags this change should be restricted to something like
"VerticalAxisGroup\s*#\'minimum-Y-extent". That would be a different issue,
and I am about to report it in combination with a closely-related missing converty-ly
rule.
-
Keith
(*1) One might wonder why VerticalAxisGroup supports the grob-interface, being
that it is not a graphical object, but that question seems outside the scope of
this issue.