Updates:
Status: Verified
Comment #15 on issue 305 by brownian.box: positioning of hairpins and
dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
Sorry then.
Thank you, verified.
___
bug-lilypond mailing list
bug-lilypond@gn
Updates:
Status: Fixed
Labels: fixed_2_13_23
Comment #14 on issue 305 by n.puttock: positioning of hairpins and dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
Automatic breaking isn't supported yet; you have to tell LilyPond where to
end the
alignment spanner:
Updates:
Status: Accepted
Labels: -fixed_2_13_23
Comment #13 on issue 305 by brownian.box: positioning of hairpins and
dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
2.13.23 still puts hairpin below staff (see initial example).
__
Updates:
Status: Fixed
Labels: fixed_2_13_23
Comment #12 on issue 305 by n.puttock: positioning of hairpins and dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
(No comment was entered for this change.)
___
bug-lilypond
Updates:
Labels: -Patch
Comment #11 on issue 305 by percival.music.ca: positioning of hairpins and
dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
Patch has been withdrawn by Nick.
--
You received this message because you are listed in the owner
or CC fields of this i
Updates:
Labels: Patch
Comment #10 on issue 305 by n.puttock: positioning of hairpins and dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
Patch: http://codereview.appspot.com/129073
--
You received this message because you are listed in the owner
or CC fields of this iss
Comment #9 on issue 305 by n.puttock: positioning of hairpins and dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
Issue 999 has been merged into this issue.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this i
Updates:
Owner: n.puttock
Comment #8 on issue 305 by n.puttock: positioning of hairpins and dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of this iss
Updates:
Status: Started
Comment #7 on issue 305 by n.puttock: positioning of hairpins and dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of this issu
Issue 305: positioning of hairpins and dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
Comment #6 by lemzwerg:
Ah, ok. Yes, I think this would help.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
Issue 305: positioning of hairpins and dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
Comment #5 by hanwenn:
the break refers to breaking the alignment spanner that normally aligns
the two.
--
You received this message because you are listed in the owner
or CC fields of this
Issue 305: positioning of hairpins and dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
Comment #4 by lemzwerg:
Well, this `normally' isn't true for more complicated music, cf.
hairpin-dynamic2.png
-- how would `break-alignment' work? The name of this property implies
that there
Issue 305: positioning of hairpins and dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
Comment #3 by hanwenn:
Actually, there is just one line of dynamics per voice, and they
normally should be
aligned. I can add a special 'break-alignment' event to support this though.
Issue
Issue 305: positioning of hairpins and dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
Comment #2 by lemzwerg:
The hairpin should appear above the staff (due to the `^').
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
Issue 305: positioning of hairpins and dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
Comment #1 by hanwenn:
I don't understand this image. What's the point?
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred thi
15 matches
Mail list logo
