Updates:
Status: Verified
Comment #14 on issue 1723 by ma...@gregoriana.sk: beam fails to extend over
rest, intermittently
http://code.google.com/p/lilypond/issues/detail?id=1723
(No comment was entered for this change.)
___
bug-lilypond m
Comment #12 on issue 1723 by d...@gnu.org: beam fails to extend over rest,
intermittently
http://code.google.com/p/lilypond/issues/detail?id=1723
It was a case of reading past the end of an array into uninitialized
memory.
If infos.size() is zero for some reason when entering this functi
Updates:
Status: Fixed
Labels: fixed_2_15_20
Comment #11 on issue 1723 by k-ohara5...@oco.net: beam fails to extend over
rest, intermittently
http://code.google.com/p/lilypond/issues/detail?id=1723
Fix pushed to staging in 7ee874c
It was a case of reading past the end of an a
"m...@apollinemike.com" writes:
> On Nov 17, 2011, at 3:22 PM, lilyp...@googlecode.com wrote:
>
>>
>> Comment #10 on issue 1723 by d...@gnu.org: beam fails to extend over
>> rest, intermittently
>> http://code.google.com/p/lilypond/issues/detail?id=1723
>>
>> Previous comment 9 was a wrong lead
On Nov 17, 2011, at 9:22 PM, lilyp...@googlecode.com wrote:
>
> Comment #10 on issue 1723 by d...@gnu.org: beam fails to extend over rest,
> intermittently
> http://code.google.com/p/lilypond/issues/detail?id=1723
>
> Previous comment 9 was a wrong lead, just a case of obfuscate programming.
On Nov 17, 2011, at 3:22 PM, lilyp...@googlecode.com wrote:
>
> Comment #10 on issue 1723 by d...@gnu.org: beam fails to extend over rest,
> intermittently
> http://code.google.com/p/lilypond/issues/detail?id=1723
>
> Previous comment 9 was a wrong lead, just a case of obfuscate programming.
Comment #10 on issue 1723 by d...@gnu.org: beam fails to extend over rest,
intermittently
http://code.google.com/p/lilypond/issues/detail?id=1723
Previous comment 9 was a wrong lead, just a case of obfuscate programming.
I'll likely commit some programming comments to save somebody else fr
Comment #9 on issue 1723 by d...@gnu.org: beam fails to extend over rest,
intermittently
http://code.google.com/p/lilypond/issues/detail?id=1723
If the "continue" in lily/beam.cc:471 triggers on the second run through
the do loop starting in l.448, any values placed into "current" on the
Comment #8 on issue 1723 by d...@gnu.org: beam fails to extend over rest,
intermittently
http://code.google.com/p/lilypond/issues/detail?id=1723
Ok, some sleuthing. The last example I posted is actually quite
instructive. It shows that it is hit&miss for every single occurence: the
left
Comment #7 on issue 1723 by d...@gnu.org: beam fails to extend over rest,
intermittently
http://code.google.com/p/lilypond/issues/detail?id=1723
When it rains, it pours.
Attachments:
beam-broken-difficult.png 11.2 KB
beam-broken-difficult.details.html 1006 bytes
_
Comment #6 on issue 1723 by d...@gnu.org: beam fails to extend over rest,
intermittently
http://code.google.com/p/lilypond/issues/detail?id=1723
"Unable to work on": no. It just throws a spanner in our regression tests:
one frequently needs to manually examine a change and shrug it off.
Updates:
Labels: -Priority-Medium
Comment #5 on issue 1723 by gra...@percival-music.ca: beam fails to extend
over rest, intermittently
http://code.google.com/p/lilypond/issues/detail?id=1723
priority-medium: we decided not to use "priority" any more, but it's a
waste of time to have
Comment #4 on issue 1723 by d...@gnu.org: beam fails to extend over rest,
intermittently
http://code.google.com/p/lilypond/issues/detail?id=1723
Is there a reason this is Priority-Medium? It's not just incorrect output,
it also messes with regression testing. In my opinion, it does not ma
Updates:
Summary: beam fails to extend over rest, intermittently
Labels: -Priority-High Priority-Medium
Comment #3 on issue 1723 by k-ohara5...@oco.net: beam fails to extend over
rest, intermittently
http://code.google.com/p/lilypond/issues/detail?id=1723
This occurs intermitt
14 matches
Mail list logo
