Issue 442: request: RemoveEmptyStaffContext  reducing PianoStaff to one staff
http://code.google.com/p/lilypond/issues/detail?id=442

New issue report by gpermus:
When typesetting an orchestral score with Piano or Harp parts, and using
RemoveEmptyStaffContext, the PianoStaff can sometimes be reduced to one
single staff (for instance when only one hand is playing).

This doesn't seem to be the right engraving rule in orchestral scores,
where both staves are usually preserved wherever there's enough space
on the page.

Here's Kieren suggestion to deal with this issue:
---------- Forwarded message ----------
From: Kieren MacMillan <[EMAIL PROTECTED]>
Date: 26 août 2007 17:47

IMO, this should be a setting similar to connectArpeggios -- say,
keepAliveTogether -- where the default is ##t, but it can be set to
##f as desired. I suppose this could also be extended (as an
interface) to ChoirStaff, StaffGroup, etc., for ultimate flexibility.
----------------------------------------------------

In the following example, the piano staves should only be hidden in
the third system.

%%%%

one = {
  \repeat unfold 4 { a4 b c' d'} \break
  \repeat unfold 4 { a4 b c' d'} \break
  \repeat unfold 4 { a4 b c' d'} \break
  a1
}
two = { \clef bass
  \repeat unfold 4 { a4 b c' d'} \break
  \repeat unfold 4 { a4 b c' d'} \break
  R1*4 \break
  a1
}
three = { \clef bass
  \repeat unfold 4 { a4 b c' d'} \break
  R1*4 \break
  R1*4 \break
  a1
}
\score {<<
    \context Staff = one \one
    \new PianoStaff <<
      \context Staff = two \two
      \context Staff = three \three >>
    >>
    \layout {
        \context { \RemoveEmptyStaffContext }
    }
}

%%%%




Issue attributes:
        Status: Accepted
        Owner: gpermus
        Labels: Type-Enhancement Priority-Low

-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings


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

Reply via email to