Status: Accepted
Owner: ----
Labels: Type-Ugly Regression

New issue 4316 by [email protected]: DynamicLineSpanner.outside-staff-priority = ##f fails since 2.19.14
https://code.google.com/p/lilypond/issues/detail?id=4316

On 06/03/15 21:25, Simon Albrecht wrote:> Hello,

after Phil and Thomas could do some more to enlighten the problem I had,
and confirmed that it seems to be a regression, I now direct this again
to the bug-list. Thomas made a minimal example (see at the bottom, with
output attached).

Thanks everybody,
Simon


-------- Weitergeleitete Nachricht --------
Betreff:     Re: Re: Dynamics negative Y-offset
Datum:     Fri, 6 Mar 2015 01:45:54 +0100
Von:     Thomas Morley <[email protected]>
An:     Simon Albrecht <[email protected]>
Kopie (CC):     lilypond-user <[email protected]>, Phil Holmes
<[email protected]>





2015-03-05 17:12 GMT+01:00 Simon Albrecht <[email protected]
<mailto:[email protected]>>:

    I assume it was an oversight that you didn’t include the list…
    This also shows that there is no link to any alignment changes,
    which happened earlier (around 2.10).

    Yours, Simon


    -------- Weitergeleitete Nachricht --------
    Betreff:     Re: Dynamics negative Y-offset
    Datum:     Thu, 5 Mar 2015 16:09:27 -0000
    Von:     Phil Holmes <[email protected]> <mailto:[email protected]>
    An:     Simon Albrecht <[email protected]>
    <mailto:[email protected]>



    Narrowing this down a bit, the change occurred between 19.12 and
19.14, and
    the failure to tweak happens whether the tweak is applied via the
function
    or directly:


{
   \set Staff.instrumentName = #(lilypond-version)
   \dynamicUp
 %  \override DynamicText.outside-staff-priority = ##f
   \override DynamicLineSpanner.outside-staff-priority = ##f
   c'-\tweak Y-offset -1 \f
 }

 returns different output on my Linux-machine for 2.18.0 and 2.19.16 (see
 attached)
 I lean towards regarding it buggy

 Cheers,
  Harm

Attachments:
        atest-2-19-16.png  1.6 KB
        atest-2-18-0.png  1.6 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

Reply via email to