ps printing the barcheck warnings after a while, or perhaps
one that issues new warnings only when there is a change in how far barchecks
are misaligned (so that we report when new mistakes are being done).
As an example, consider the following:
\score { \notes <<
\new Staff="A" {c
[EMAIL PROTECTED] writes:
> One rule could be to not print the "barcheck failure at a/b" warning in a bar,
> if a "barcheck failure at a/b" with the same a and b occured on the last | of
> the same staff. But probably there also exist even more clever mechanisms.
Your proposal seems clever enoug
[EMAIL PROTECTED] writes:
> future if it works fine, barcheck failures is not exactly something you plan
> to do :) )
>
> > > Also, I have noticed that midi and paper seem to have separate barcheck
> > > mechanisms, the paper's being a bit more intelligent. Included in my wish
> > > is that both
On Friday 09 January 2004 01.47, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > One rule could be to not print the "barcheck failure at a/b" warning in a
> > bar, if a "barcheck failure at a/b" with the same a and b occured on the
> > last | of the same staff. But probably there also exist
[EMAIL PROTECTED] writes:
> But this is getting complicated. IMHO the only important difference is between
> O(1) and O(# of bars), the rest is just cosmetics.
>
> (and I hope the barCheckSynchronize can be defaulted to #t sometime in the
> future if it works fine, barcheck failures is not exact
> > > > Also, I have noticed that midi and paper seem to have separate
> > > > barcheck mechanisms, the paper's being a bit more intelligent.
> > > > Included in my wish is that both barcheck mechanisms should follow
> > > > the same rules.
> > >
> > > Can you demonstrate this? This hasn't been the
On Friday 09 January 2004 01.47, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > One rule could be to not print the "barcheck failure at a/b" warning in a
> > bar, if a "barcheck failure at a/b" with the same a and b occured on the
> > last | of the same staff. But probably there also exist
> > > Your proposal seems clever enough. I've added this, but you have to
> > > set barCheckSynchronize to #f for it to work.
> >
> > Thanks a lot! This new barcheck is just great. It's now harder than I
> > expected to fool it into doing O(n) warnings (and I'm not sure it uses
> > exactly my sugge
[EMAIL PROTECTED] writes:
> > Your proposal seems clever enough. I've added this, but you have to
> > set barCheckSynchronize to #f for it to work.
>
> Thanks a lot! This new barcheck is just great. It's now harder than I expected
> to fool it into doing O(n) warnings (and I'm not sure it uses e
You have many ideas, but the point of barcheck is to indicate
errors. I think that it is pointless to be pedantically correct if
errors have already been detected. For the last case, I can imagine
your reasoning, but \addlyrics (and its more modern friend
\newaddlyrics) are enough of a bitch to get
Hi,
Incorrect midi barcheck warnings are happening again. This time I was unable
to isolate what causes it; random & unrelated changes seem to affect it. I
couldn't get it much smaller than this:
%Lilypond produces correct output, but during midi output, it produces a
%barcheck wa
Status: Accepted
Owner:
Labels: Type-Scripts Priority-Medium
New issue 1626 by philehol...@googlemail.com: Atriculate produces faulty
barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
Reported by Helge Hafting
Using articulate.ly and the \mark command causes
Updates:
Summary: Articulate produces faulty barcheck warnings
Comment #1 on issue 1626 by philehol...@googlemail.com: Articulate produces
faulty barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
Spelling correction
Updates:
Labels: Patch-review
Comment #2 on issue 1626 by philehol...@googlemail.com: Articulate produces
faulty barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
Patch that is said to fix this.
Attachments:
articulate-barcheck.patch.patch 1.8 KB
Comment #3 on issue 1626 by percival.music.ca: Articulate produces faulty
barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
patch here:
http://codereview.appspot.com/4435069
___
bug-lilypond mailing list
bug-lilypond
Comment #4 on issue 1626 by percival.music.ca: Articulate produces faulty
barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
does anybody have an email address for Helge Hafting? I'd like to make
sure that he (or she? who knows with German names) gets credi
On 01. mai 2011 19:24, lilyp...@googlecode.com wrote:
Comment #4 on issue 1626 by percival.music.ca: Articulate produces
faulty barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
does anybody have an email address for Helge Hafting? I'd like to make
Both helge
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_0
Comment #5 on issue 1626 by percival.music.ca: Articulate produces faulty
barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
pushed
d4c5b03afa8384ee50a7b9536485bc26d14033aa
Updates:
Status: Verified
Comment #6 on issue 1626 by colinpkc...@gmail.com: Articulate produces
faulty barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
Verified 2.15.0
___
bug-lilypond mailing list
bug-lilypond
Updates:
Status: Fixed
Comment #7 on issue 1626 by colinpkc...@gmail.com: Articulate produces
faulty barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
Unverified in 2.13.61
___
bug-lilypond mailing list
bug
Updates:
Status: Verified
Comment #8 on issue 1626 by colinpkc...@gmail.com: Articulate produces
faulty barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
Re-verified 2.15, by golly!
___
bug-lilypond mailing list
>>>>> "lilypond" == lilypond writes:
lilypond> Updates: Status: Verified
lilypond> Comment #8 on issue 1626 by colinpkc...@gmail.com:
lilypond> Articulate produces faulty barcheck warnings
lilypond> http://code.google.com/p/lilypond/issues/detail?id=1626
On 11-06-26 06:28 PM, Peter Chubb wrote:
"lilypond" == lilypond writes:
lilypond> Updates: Status: Verified
lilypond> Comment #8 on issue 1626 by colinpkc...@gmail.com:
lilypond> Articulate produces faulty barcheck warnings
lilypond> http://code.google.com/p/lilypond
>>>>> "Colin" == Colin Campbell writes:
Colin> On 11-06-26 06:28 PM, Peter Chubb wrote:
>>>>>>> "lilypond" == lilypond writes:
lilypond> Updates: Status: Verified
>>
lilypond> Comment #8 on issue 1626 by colinpkc...@gma
Updates:
Labels: fixed_2_14_0
Comment #9 on issue 1626 by carl.d.s...@gmail.com: Articulate produces
faulty barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
(No comment was entered for this change.)
___
bug
25 matches
Mail list logo
