Re: [Lilypond-auto] Issue 3307 in lilypond: Rest positions incorrect with non-standard line count

[lilypond]

Updates:
        Status: Fixed
        Labels: -Needs-design -Patch-countdown Fixed_2_17_18

Comment #59 on issue 3307 by address@hidden: Rest positions incorrect with  
non-standard line count
http://code.google.com/p/lilypond/issues/detail?id=3307

Ok, countdown is ended and there has not been additional commentry.   
Comment #51 still holds: configurability would be nice to have.  I am  
putting this out in the current form, however, as it is important to get at  
least the default reviewed, and it appears that as a default it is  
reasonable.

Pushed to staging as merge commit
*   commit 2f36dbf850efac7df59b39f32329714c1a20d251
|\  Merge: 71aa65a 6625efe
| | Author: David Kastrup <address@hidden>
| | Date:   Tue Apr 30 12:59:46 2013 +0200
| |
| |     Merge branch 'issue3307' into HEAD
| |
| |     This merges the work for
| |
| |     Issue 3307: Rest positions incorrect with non-standard line count
| |
| |     into master as a single commit since the intermediate changes are  
not
| |     thoroughly tested (though expected to be incrementally compilable).
| |
| * commit 6625efe114fb04b18d60fae2c571cdacaf6bef7e
| | Author: David Kastrup <address@hidden>
| | Date:   Wed Apr 10 21:53:11 2013 +0200
| |
| |     Get consistent vertical position for church rests
| |
| * commit 19503a9141bd5afb833036f4d36b6062055b6f79
| | Author: David Kastrup <address@hidden>
| | Date:   Wed Apr 10 18:53:33 2013 +0200
| |
| |     Make MultiMeasureRests use the same positioning mechanism as normal  
rests
| |
| * commit 9214fc9912ee14c29aa523f880c97b12bf5a2d17
| | Author: David Kastrup <address@hidden>
| | Date:   Tue Apr 9 19:17:25 2013 +0200
| |
| |     Issue 3307: Rest positions incorrect with non-standard line count
| |
| * commit 028ca52e641777e0eb12a4e44a0f662d1295a357
|/  Author: David Kastrup <address@hidden>
|   Date:   Wed Apr 17 18:53:44 2013 +0200
|
|       Add rest-positioning regtest
|


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