Updates:
Status: Verified
Comment #11 on issue 1353 by pnorcks: chordnames may move erratically on
the page on OSX 10.6
http://code.google.com/p/lilypond/issues/detail?id=1353
Looks good.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Updates:
Status: Fixed
Owner: Carl.D.Sorensen
Labels: fixed_2_13_47
Comment #10 on issue 1353 by carl.d.s...@gmail.com: chordnames may move
erratically on the page on OSX 10.6
http://code.google.com/p/lilypond/issues/detail?id=1353
I can see no problem with adding Chor
Comment #9 on issue 1353 by jameseli...@googlemail.com: chordnames may move
erratically on the page on OSX 10.6
http://code.google.com/p/lilypond/issues/detail?id=1353
I don't know if an enhancement or bug is the proper method here, apparently
ChordNames is included by default in:
• ChoirS
Comment #8 on issue 1353 by pkx1...@hotmail.com: chordnames may move
erratically on the page on OSX 10.6
http://code.google.com/p/lilypond/issues/detail?id=1353
Is this a bug or 'expected' behaviour and if so, we perhaps need a doc
update?
I don't know if this an @knownissue or a bug (in
Comment #6 on issue 1353 by byu9...@gmail.com: chordnames may move
erratically on the page on OSX 10.6
http://code.google.com/p/lilypond/issues/detail?id=1353
So does this issue now become invalid, since the mistake is putting a
ChordNames context in a context that doesn't accept it?
Or w
Comment #5 on issue 1353 by n.puttock: chordnames may move erratically on
the page on OSX 10.6
http://code.google.com/p/lilypond/issues/detail?id=1353
however the chords are above the top staff and no longer below the staff.
That's correct for the snippet above since \chords is the first c
Comment #4 on issue 1353 by pkx1...@hotmail.com: chordnames may move
erratically on the page on OSX 10.6
http://code.google.com/p/lilypond/issues/detail?id=1353
No I don't have the issue anymore if I use this construct however the
chords are above the top staff and no longer below the staff
Comment #3 on issue 1353 by jameseli...@googlemail.com: chordnames may move
erratically on the page on OSX 10.6
http://code.google.com/p/lilypond/issues/detail?id=1353
Adding ChordNames to PianoStaff looks like it solves the problem for me. I
don't get the erratic output.
___
Comment #2 on issue 1353 by n.puttock: chordnames may move erratically on
the page on OSX 10.6
http://code.google.com/p/lilypond/issues/detail?id=1353
Do you still get the erratic behaviour if you allow ChordNames to be
accepted by PianoStaff?
\layout {
\context {
\PianoStaff
\a
Comment #1 on issue 1353 by pkx1...@hotmail.com: chordnames may move
erratically on the page on OSX 10.6
http://code.google.com/p/lilypond/issues/detail?id=1353
Note that this only occurs when using \new PianoStaff <<..>> or \new
GrandStaff <<..>>. All other staff-types or just using <<...>
Status: Accepted
Owner:
Labels: Type-Defect Priority-High OpSys-OSX
New issue 1353 by jameseli...@googlemail.com: chordnames may move
erratically on the page on OSX 10.6
http://code.google.com/p/lilypond/issues/detail?id=1353
Compiling the following input on mac OSX 10.6 successively yie
11 matches
Mail list logo
