lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: lilypond
Subject: Re: [Lilypond-auto] Issue 3279 in lilypond: space consecutive tempo marks
Date: Mon, 08 Apr 2013 18:28:55 +0000


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

Collision avoidance for objects that align above fixed objects (that
use the break-align interface) is purely vertical.

That might be a limitation we could/want to get rid of.
But it is not only for tempo/marks indications, the same applies to
TextScript, Script, Dynamics etc. and any other outside-staff object
(inside-staff maybe as well).


The placement rules pick the first object from the givne list that
is present, which is generally useful, so placing the rehearsal mark
objects where something else /would be/ is tricky.

I don't agree.  RehearsalMark should align on barline.
There is no barline position at line break (begin of line), but one
could see where the barline /would be/ based on repeat volta
(see comments 12 & 13).  Issue 1150 states that LilyPond does not
correctly align RehearsalMark on this position.

I don't understand why "begin-of-line barline position" is correct when
LilyPond print a begin-of-repeat-volta barline, but not when there is
no special barline at begin-of-line.


Possibly.  That is the set of rules I originally proposed; see image
in comment #1

It's hard to tell where the first note (NoteColumn) would be for
more-than-one-measure MMR.
And I agree with Werner that it seems too far to the right.
BUT tempo indications always left-aligned on KeySignature (when there
is a MMR or not) is not the solution IMHO (for both situations).


If a partial solution based on the existing system is not acceptable,
this will wait until version 2.20.

I'm sorry, I do not mean to disagree just "for the pleasure", but I do
not think it does a service to implement half flawed solution.


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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]