1 Dec 10:06
Re: Dynamics collision in 2.11.64
From: Dmytro O. Redchuk <brownian.box <at> gmail.com>
Subject: Re: Dynamics collision in 2.11.64
Newsgroups: gmane.comp.gnu.lilypond.general
Date: 2008-12-01 09:06:04 GMT
Subject: Re: Dynamics collision in 2.11.64
Newsgroups: gmane.comp.gnu.lilypond.general
Date: 2008-12-01 09:06:04 GMT
2008/11/29 Neil Puttock <n.puttock <at> gmail.com>: > Hi Dmytro, > >> As you can see (attached), there is everything ok with 2.11.42. > > The Bar_engraver is responsible for aligning the end points of line > spanners with a barline when 'to-barline = ##t; it pays no attention > to scripts which directly follow a spanner. Thank you for explanation. However... i'd say that default behavour became... strange?.. Wouldn't it better to have 'to-barline = ##f by default -- in this case one (in this situation -- me,-) shouldn't re-check visually all hairpins?(Continue reading)Yes, i can believe, that #'self-alignment-X = #RIGHT for DynamicText is uncommon, but... current settings for 'to-barline actually means "collide by default", i'd say. Well, wether i do convert-ly or type a new score -- dynamics collide by default with 'to-barline = ##t. *If* i have #'self-alignment-X = #RIGHT for DynamicText. "Have i missed or messed smth *again*?" (mt)
> Regards, > Neil -- --
Yes, i can believe, that #'self-alignment-X = #RIGHT for DynamicText is
uncommon, but... current settings for 'to-barline actually means
"collide by default",
i'd say. Well, wether i do convert-ly or type a new score -- dynamics
collide by default
with 'to-barline = ##t. *If* i have #'self-alignment-X = #RIGHT for DynamicText.
"Have i missed or messed smth *again*?" (mt)
RSS Feed