Re: [Lilypond-auto] Issue 4316 in lilypond: Reconsider behaviour of DynamicText and DynamicLineSpanner with outside-staff-priority and Y-offset

[lilypond]

Updates:
	Summary: Reconsider behaviour of DynamicText and DynamicLineSpanner with  
outside-staff-priority and Y-offset

Comment #11 on issue 4316 by address@hidden: Reconsider behaviour of  
DynamicText and DynamicLineSpanner with outside-staff-priority and Y-offset
https://code.google.com/p/lilypond/issues/detail?id=4316

(That was written in parallel.)

I see. I thought Y-offset was unset by default.
extra-offset is no use, of course, since it bypasses any layout decisions.
I wasn’t aware of \offset; that can be used to deal with that ‘sub-bug’.  
Thanks for the hint.

Still there is the problem that for moving a single DynamicText into the  
staff, four (or five) properties need to be overridden: the  
outside-staff-priority and Y-offset of both DynamicText and  
DynamicLineSpanner, plus eventually X-offset of DynamicText (unrelated).  
One would expect the override on DynamicLineSpanner.Y-offset to be  
unnecessary, but confusingly it is required; the following will not work:

{
  c''
  -\tweak outside-staff-priority ##f
  -\tweak DynamicLineSpanner.outside-staff-priority ##f
  -\tweak Y-offset 2.05
  %-\tweak DynamicLineSpanner.Y-offset 0 %uncommenting this makes it work
  \p
}

I’ll spend some further thought on how to wrap this for everyday use.

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