Re: Odd layout choices

2014-09-18 Thread Guy Stalnaker

Simon,

Thanks, again. It does help :-)

On 09/18/2014 07:34 AM, Simon Albrecht wrote:

(continuing the thread on ly-user)

Hello Guy,

no, there isn't, because it tends to contradict the logic: they won't
appear to be simultaneous, if they are placed one after another.
You might try the methods described in

.
For the dynamics, this can be complicated, but try:
\override DynamicText.X-offset or
\override DynamicLineSpanner.outside-staff-priority = ##f (to be placed
in \layout) and
\override DynamicText.Y-offset and similar.

HTH, Simon


Am 16-Sep-2014 06:31:50 +0200 schrieb jimmyg...@gmail.com:

No longer baffling :-) Using the min-systems-per-page option forced
LP to put the systems on the same page and it is clear, when it does
so, why its default fitting algorithm does not! It appears to be the
non-musical elements that are interfering with things. I still had
to play with margins, etc. to get it to look "right." Thanks for
your help. Is there an easy way to tell Lilypond not to stack
vertically simultaneous directives like "a tempo" and dynamics, but
to render them horizontally?



--

"There is only love, and then oblivion. Love is all we have
to set against hatred." (paraphrased) Ian McEwan

Guy Stalnaker
jimmyg...@gmail.com

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Odd layout choices

2014-09-18 Thread Simon Albrecht
(continuing the thread on ly-user)

Hello Guy,

 no, there isn't, because it tends to contradict the logic: they won't appear 
to be simultaneous, if they are placed one after another.
You might try the methods described in . For the dynamics, this can be 
complicated, but try:
\override DynamicText.X-offset or
\override DynamicLineSpanner.outside-staff-priority = ##f (to be placed in 
\layout) and
\override DynamicText.Y-offset and similar.

HTH, Simon 

 Am 16-Sep-2014 06:31:50 +0200 schrieb jimmyg...@gmail.com: 
  No longer baffling :-) Using the min-systems-per-page option forced LP to put 
the systems on the same page and it is clear, when it does so, why its default 
fitting algorithm does not! It appears to be the non-musical elements that are 
interfering with things. I still had to play with margins, etc. to get it to 
look "right." Thanks for your help. Is there an easy way to tell Lilypond not 
to stack vertically simultaneous directives like "a tempo" and dynamics, but to 
render them horizontally?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user