|
From: | Han-Wen Nienhuys |
Subject: | Re: Using \global - Lilypond 2.9.20 Windows |
Date: | Thu, 05 Oct 2006 14:24:59 +0200 |
User-agent: | Thunderbird 1.5.0.7 (X11/20060927) |
Erik Sandberg schreef:
On Wednesday 04 October 2006 10:33, Han-Wen Nienhuys wrote:Mats Bengtsson schreef:really well-defined which one and the program should definitely tell that that the user probably has made a mistake and the program had to make a decision on which mark to typeset. In your case, you know why the warning appears and you know that you can ignore it, since you only have \mark commands in your \global. If you want to get rid of the warnings, you could add the \mark commands in a separate variable that's only included at the top stave of the score, or you could use the \tag feature to do the same thing.It would be better if there were a check if the new event is equal tothe old one, and only warn if they're different.Hm, then I'll define a new equal_p for probs. I'd say that two events are equal if all event properties are 'equal?'. This includes 'origin, so there will be a warning in cases like:
Hmmm. Good question. I'd rather think that origin should not be part of the equality test, but let's see what happens.
<< c8 \mark "A" \mark "A" I think this is desirable; it catches cases like c4 ( -. -_ -- \( ( where a user sends two slur-start-events by mistake.Also, the definition location seems to be missing. Erik?My work-in-progress macro-capable parser contains a generic fix for this, where I added a mandatory location parameter to MY_MAKE_MUSIC. Should I try to backport this before 2.10?
Yes, I think that's a good idea. -- Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com
[Prev in Thread] | Current Thread | [Next in Thread] |