Re: [Lilypond-auto] Issue 3518 in lilypond: Support temporary divisi staves

[lilypond]

Comment #12 on issue 3518 by address@hidden: Support temporary divisi staves
http://code.google.com/p/lilypond/issues/detail?id=3518

Ok, I think I like the idea of using something like \separateStaff and  
\shareStaff even though I don't like their names.  They can just output a  
spanner with a unique interface that is all that keeps a divisiStaff  
alive.  That simplifies the whole mess _severely_, not requiring three  
different sources with swapping of items-worth-living-for and other  
nonsense.

So we need a new spanner with an interface of its own.  The only remaining  
issue is the means for killing the spurious non-divisi staff whenever it  
should disappear.  Either it is a property of the spanner (you specify  
something like \separateStavesFor "nondivisi" ... \oneStaff), or it is a  
property of the staff.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings