On 3/15/06, Trevor Bača <[EMAIL PROTECTED]> wrote:
> On 3/15/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> > Trevor Bača wrote:
> > > On 3/15/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> > >
> > >>Trevor Bača wrote:
> > >>
> > >>>This is a weird one. If you have the following three conditions ...
> > >>>
> > >>
> > >>yes, it's a build issue. Only MacOS has this problem.
> > >
> > >
> > > Ah, yes. Sorry I didn't mention: I am, in fact, on OS X.
> >
> > can you see if you can further reduce it? ie. less notes, less
> > measures, etc.
>
> Only shows up if the combination of the number of notes together with
> the make-moment value to proportionalNotationDuration causes the
> beamed part of the expression to break across lines. So I'm having a
> hard time stretching the example out with ever smaller values to
> proportionalNotationDuration (meaning that I'm having a hard time
> reducing the overall number of notes in the example).
>
> I'll try more during lunch here next hour.
Ugh. The exact conditions to induce this bug are very difficult.
It is possible to come up with an example with somewhat fewer notes
and fewer measures, like this:
%%%%%%%% BEGIN %%%%%%%%%%%%
\version "2.7.38"
\new Score \with {
proportionalNotationDuration = #(ly:make-moment 1 256)
} <<
\new Staff {
\set allowBeamBreak = ##t
\time 2/8
c'8[
c'32 c'32 c'32 c'32
c'8
c'32 c'32 c'32 c'32
c'8
c'32 c'32 c'32 c'32]
}
>>
%%%%%%% END %%%%%%%%%%%%%
... but cutting the example down even further usually causes the
problem to no longer manifest.
--
Trevor Bača
[EMAIL PROTECTED]
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
