http://code.google.com/p/lilypond/issues/detail?id=1612
My reading of the situation is this:
1. we should turn off beam collisions for cross-staff stems
2. we should document that such beam collisions are turned off, as:
- a @knownissue in the cross-staff stem node
- in the changes.tely
3.
Reviewers: ,
Description:
Turns off beam collision for cross-staff beams
Please review this at http://codereview.appspot.com/4423062/
Affected files:
M lily/beam-collision-engraver.cc
Index: lily/beam-collision-engraver.cc
diff --git a/lily/beam-collision-engraver.cc
Reviewers: ,
Message:
I did my best to figure out a way to handle automatic beams before staff
changes, but the best I could come up with was a system where a beam was
created every time the automatic beam engraver considered starting a
beam, which leads to a lot of dead grobs that could
LGTM
http://codereview.appspot.com/4423062/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM
http://codereview.appspot.com/4431058/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Now that Mike's fixed 1612, let's look at the other remaining beaming problem.
http://code.google.com/p/lilypond/issues/detail?id=1613
This issue is still open and produces bad output with git master.
Anybody have any ideas?
Cheers,
- Graham
___
I'll have a look.
On Fri, Apr 22, 2011 at 10:55 AM, Graham Percival
gra...@percival-music.ca wrote:
Now that Mike's fixed 1612, let's look at the other remaining beaming problem.
http://code.google.com/p/lilypond/issues/detail?id=1613
This issue is still open and produces bad output with git
http://codereview.appspot.com/4373046/diff/12002/ly/event-listener.ly
File ly/event-listener.ly (right):
http://codereview.appspot.com/4373046/diff/12002/ly/event-listener.ly#newcode102
ly/event-listener.ly:102: #(define (print-line engraver values)
If you make `values' a `rest' argument you
On 18 April 2011 15:30, percival.music...@gmail.com wrote:
On 2011/04/18 14:09:52, hanwenn wrote:
In that case, it would probably be cleaner to
hook into the event listener framework directly, without having an
engraver in between. The Scheme engraver mechanism is really for
creating
Hi everybody...
I have some difficulties to understand the minimum-distance setting, I just
hopped that somebody could explain it to me.
According to current documentation, minimum-distance is the smallest allowable
vertical distance, and basic-distance the default one. So with the following
On 4/22/11 1:32 PM, Olivier Chamley olivier.cham...@free.fr wrote:
Hi everybody...
I have some difficulties to understand the minimum-distance setting, I just
hopped that somebody could explain it to me.
According to current documentation, minimum-distance is the smallest allowable
http://codereview.appspot.com/4450052/diff/1/lily/beam.cc
File lily/beam.cc (right):
http://codereview.appspot.com/4450052/diff/1/lily/beam.cc#newcode1221
lily/beam.cc:1221:
This solution doesn't work for:
\new Staff {
{ \voiceOne s16 fis'' }
\\
{ \voiceTwo e4 e }
\\
{
On Fri, Apr 22, 2011 at 6:20 PM, mts...@gmail.com wrote:
\new Staff {
{ \voiceOne s16 fis'' }
\\
{ \voiceTwo e4 e }
\\
{ \voiceFour
f''8 e'' gis'' gis'' }
}
One interesting thing is that it is the stems, not the noteheads, that
are pushing this down. If you remove
13 matches
Mail list logo