Re: [Lilypond-auto] Issue 660 in lilypond: ossia staff doesn't stop at correct horizontal position

[lilypond]

Updates:
        Labels: -Patch-review Patch-needs_work

Comment #7 on issue 660 by address@hidden: ossia staff doesn't stop at correct  
horizontal position
https://code.google.com/p/lilypond/issues/detail?id=660

Rethinking this after some experiments, this is not good at all: it stops  
at the barline regardless of whether or not a time/key/clef signature or  
something else follows, and it would be rather tricky to do that depending  
on the following stuff: the PaperColumn that this attaches to is the same  
for all staves.  One could go through the PaperColumn looking for any  
non-empty grobs belonging to the current stuff but that seems excessive and  
still second-guesses the user's intentions.

So what actually should happen is that LilyPond obeys  
Staff.StaffSymbol.to-barline (which it apparently doesn't for some  
reason).  Which may default to ##t if we find that convenient, though for  
applications like "ossia staff" you need to override other properties  
anyway so we might just keep it unset by default.

--
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