[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 4316 in lilypond: DynamicLineSpanner.outside-s
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 4316 in lilypond: DynamicLineSpanner.outside-staff-priority = ##f fails since 2.19.14 |
Date: |
Sat, 07 Mar 2015 17:43:01 +0000 |
Comment #1 on issue 4316 by address@hidden:
DynamicLineSpanner.outside-staff-priority = ##f fails since 2.19.14
https://code.google.com/p/lilypond/issues/detail?id=4316
Interesting.
3bcfbed107c26650fb7bc9cc957b5424f9187866 is the first bad commit
commit 3bcfbed107c26650fb7bc9cc957b5424f9187866
Author: David Kastrup <address@hidden>
Date: Tue Sep 2 19:14:34 2014 +0200
Issue 3849: \parenthesize\p generates programming error
Register a grob as the cause for DynamicLineSpanner rather than an
event.
The patch does not actually do anything beyond that. So previously the
tweak applied to both DynamicLineSpanner as well as DynamicText (?). Now
it only applies to DynamicText. To address DynamicLineSpanner directly,
you need to write
c'-\tweak DynamicLineSpanner.Y-offset -1 \f
now. In general, any \tweak will only directly affect DynamicText now
rather than DynamicLineSpanner. I don't think it is a bug in itself but
one might want to check what kind of (default) tweaks have changed behavior
and whether or not that can be counted as undesirable.
--
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