[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-auto
Subject:    Re: [Lilypond-auto] Issue 621 in lilypond: Dynamics should avoid cross-staff BarLines (e.g. GrandSta
From:       lilypond () googlecode ! com
Date:       2013-12-31 8:12:36
Message-ID: 25-2980476681285777133-9140809941673464925-lilypond=googlecode.com () googlecode ! com
[Download RAW message or body]

Updates:
	Status: Fixed
	Labels: -Patch-push Fixed_2_19_0

Comment #25 on issue 621 by dak@gnu.org: Dynamics should avoid cross-staff  
BarLines (e.g. GrandStaff, PianoStaff etc)
http://code.google.com/p/lilypond/issues/detail?id=621

I understand Keith's comment such that this patch does not preclude manual  
shifts for fixing the positioning if one leans towards the orthodox "human  
engravers don't anticipate the placement of dynamics when placing the  
notes" school which I am not convinced of and which precluded a more  
consistent approach (also affecting cases without span bars) like the one I  
use to be pushed previously.

Pushed to staging as
commit 9edf3715c2b2cca09785dcd015724ad3c29cba8a
Author: David Kastrup <dak@gnu.org>
Date:   Thu Dec 26 16:07:50 2013 +0100

     Issue 621: Dynamics should avoid cross-staff BarLines
     (e.g. GrandStaff, PianoStaff etc)

     Dynamics usually have extra-spacing-width set to an empty interval so
     that their placement does not cause other elements to shift.

     With span bars, however, the resulting overlap is a worse cure than
     the problem.  So this switches off the width-hiding setting of
     extra-spacing-width inside of staff groups using span bars by default.
     No extra space is allocated, so dynamics will clear the span bars only
     narrowly, a reasonable compromise.


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


[prev in list] [next in list] [prev in thread] [next in thread]