|
| From: | dak |
| Subject: | Re: Issue 754: don't transpose generic property-setting music commands (issue 7303057) |
| Date: | Fri, 08 Feb 2013 09:20:59 +0000 |
On 2013/02/08 08:40:29, dak wrote:
On 2013/02/08 04:46:27, Keith wrote: > Yesterday's patch was better.
I beg to differ. It did not address instrument definitions, or manual
settings Concretely: can you show an example of not-just-academical LilyPond source that would be change to the worse with patch applied? Do you consider it sensible that values set via \override are transposed (but only if they are not set via a callback) while values set via \tweak aren't? Can you see any internal use of \set/\override in LilyPond source (or the corresponding usage of PropertySet/OverrideProperty) that would now behave inappropriately under transposition? https://codereview.appspot.com/7303057/
| [Prev in Thread] | Current Thread | [Next in Thread] |