2.7.17: minimumVerticalExtent

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

2.7.17: minimumVerticalExtent

Daniel Johnson-2
Yesterday I upgraded from 2.7.14 to 2.7.17, and I immediately noticed
that when trying to set fixed staff-spacing for a staff group, \set
Staff.minimumVerticalExtent = ##f no longer seems to do anything.  
Consider the following example:

%%% BEGIN LILYPOND CODE %%%
\version "2.7.17"

text = \lyricmode { Hel -- lo world }

\score {
    \context ChoirStaff <<
        \context Staff = women {
            \set Staff.minimumVerticalExtent = ##f
            \set Staff.verticalExtent = #'(-6 . 2)
            \clef treble
            \context Voice = sop { c4 c c2 }
        }
        \context Lyrics = sopLyrics \lyricsto sop \text
        \context Staff = men {
            \set Staff.minimumVerticalExtent = ##f
            \set Staff.verticalExtent = #'(-2 . 6)
            \clef bass
            \context Voice = bas { c4 c c2 }
        }
     >>
}
%%% END LILYPOND CODE %%%

In 2.7.14, the lyrics would be placed exactly centered between the two
staves, regardless of collision with notes.  However, in 2.7.17 the
lyrics are pushed down by the low notes in the upper staff.  Is this a
bug, or has the behaviour of minimumVerticalExtent changed?

--Daniel


_______________________________________________
bug-lilypond mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Reply | Threaded
Open this post in threaded view
|

Re: 2.7.17: minimumVerticalExtent

Mats Bengtsson-6
If you use the absolutely latest development ("unstable") version of
LilyPond, you should be prepared for changes that are possibly not
always well documented. However, in this case, convert-ly should
convert your code to something that works in 2.7.17 (actually, as
far as I can see from convert-ly, this particular change happened
between 2.7.13 and 1.7.14.

    /Mats


Daniel Johnson wrote:

> Yesterday I upgraded from 2.7.14 to 2.7.17, and I immediately noticed
> that when trying to set fixed staff-spacing for a staff group, \set
> Staff.minimumVerticalExtent = ##f no longer seems to do anything.  
> Consider the following example:
>
> %%% BEGIN LILYPOND CODE %%%
> \version "2.7.17"
>
> text = \lyricmode { Hel -- lo world }
>
> \score {
>    \context ChoirStaff <<
>        \context Staff = women {
>            \set Staff.minimumVerticalExtent = ##f
>            \set Staff.verticalExtent = #'(-6 . 2)
>            \clef treble
>            \context Voice = sop { c4 c c2 }
>        }
>        \context Lyrics = sopLyrics \lyricsto sop \text
>        \context Staff = men {
>            \set Staff.minimumVerticalExtent = ##f
>            \set Staff.verticalExtent = #'(-2 . 6)
>            \clef bass
>            \context Voice = bas { c4 c c2 }
>        }
>     >>
> }
> %%% END LILYPOND CODE %%%
>
> In 2.7.14, the lyrics would be placed exactly centered between the two
> staves, regardless of collision with notes.  However, in 2.7.17 the
> lyrics are pushed down by the low notes in the upper staff.  Is this a
> bug, or has the behaviour of minimumVerticalExtent changed?
>
> --Daniel
>
>
> _______________________________________________
> bug-lilypond mailing list
> [hidden email]
> http://lists.gnu.org/mailman/listinfo/bug-lilypond

--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463
         Fax:   (+46) 8 790 7260
        Email: [hidden email]
        WWW: http://www.s3.kth.se/~mabe
=============================================


_______________________________________________
bug-lilypond mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Reply | Threaded
Open this post in threaded view
|

Re: 2.7.17: minimumVerticalExtent

Daniel Johnson-2
Mats Bengtsson wrote:

> If you use the absolutely latest development ("unstable") version of
> LilyPond, you should be prepared for changes that are possibly not
> always well documented. However, in this case, convert-ly should
> convert your code to something that works in 2.7.17 (actually, as
> far as I can see from convert-ly, this particular change happened
> between 2.7.13 and 1.7.14.
>
>    /Mats

Aha!  It hadn't occurred to me to try convert-ly.  Just for the record,
the syntax change is as following:

Old style:
    \set Staff.minimumVerticalExtent = ##f
New style:
    \override Staff.VerticalAxisGroup #'minimum-Y-extent = ##f

Many thanks!

--Daniel

P.S. For the record, I keep the latest of both the 2.6 and 2.7 branches
installed, in /usr/local/bin and /usr/bin respectively; I have aliased
"lilypond" to the 2.7 branch, and "lily26" to the 2.6 in my .bashrc.


_______________________________________________
bug-lilypond mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/bug-lilypond