Re: [Lilypond-auto] Issue 3279 in lilypond: space consecutive tempo marks

[lilypond]

Updates:
        Labels: -Type-Enhancement -Patch-abandoned Type-Ugly Patch-new

Comment #31 on issue 3279 by address@hidden: space consecutive tempo  
marks
http://code.google.com/p/lilypond/issues/detail?id=3279

Let's try this again.

Re: comment 25 on the RehearsalMark, the compromise (between satisfying  
issue 1150 and reducing the incidence of needing to raise mark above a  
tempo) is no longer a compromise.  The output agrees with the evidence of  
common practice shown in issue 1150.  Users wanting different from common  
practice can override.

Collisions are resolved horizontally when possible (in the image, [Mark]  
Più mosso) and vertically ([D] Meno Mosso) if that is the only way to honor  
the alignment specified according to the documented  
break-alignment-interface (link to manual above).

Re: comment 25 on the "Larghissimo", the current patch goes back to  
textbook rules.  Users wanting different can override as in comment #16.   
The location where the first note 'would be' is the location where a note  
appears when another staff is added (image).

Re: implementing a half-flawed solution.  The half-flawed solution is  
already implemented; this patch merely changes the defaults so that we can  
use the half (more like 80%) that works.  Sophisticated users are resorting  
to fractional spacer rests  
<https://lists.gnu.org/archive/html/lilypond-devel/2013-02/msg00075.html>  
to solve the same issue.

http://codereview.appspot.com/8189043/

Attachments:
        tempo.ly  988 bytes
        tempo.jpg  27.2 KB

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