Re: [Lilypond-auto] Issue 3568 in lilypond: bendAfter affected by bar numbers

[lilypond]

Comment #5 on issue 3568 by address@hidden: bendAfter affected by bar  
numbers
http://code.google.com/p/lilypond/issues/detail?id=3568

Bar numbers have an outside-staff-priority and are moved to the extremal  
staff and have empty extra spacing width, so they won't effect note spacing.

The issue is connected to the box/skyline dichotomy because the right bound  
of the spanner is the current column (see bend-engraver.cc).  The current  
column is a NonMusicalPaperColumn, which is as fat as its fatest member,  
which is the bar number.  The spanner uses the full extent of the box  
around the NonMusicalPaperColumn to fix its bound (see line 912 of  
output-lib.scm).  If, however, the spanner had some sort of horizontal  
skyline and measured this against the NonMusicalPaperColumn's horizontal  
skyline, it wouldn't collide.

A much simpler solution would be to make a scheme version of  
Axis_group_interface::generic_bound_extent that could be accessed from  
bend::print.  This is the function that several spanners  
(pedal-piano-bracket, line-spanner, hairpin) use to get the extents of  
bounding items and that's how they avoid this problem.  This solution made  
sense when one could use only the extents of bounds, but it could be done  
away with now that better skylines exist (assuming that this wouldn't cause  
a performance hit).

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