Re: Issue 36 in lilypond: collision cresc and kneed beams

[lilypond]

Updates:
        Owner: address@hidden
        Labels: Patch-new

Comment #4 on issue 36 by address@hidden: collision cresc and kneed beams
http://code.google.com/p/lilypond/issues/detail?id=36

From Mike:

--snip--

Message:
I think that this is sufficient to "fix" issue 36.  As Graham points out
in the tracker, it is difficult to imagine what a good solution is, and
I have a feeling that the solution likely depends upon the user's
preferences.  In certain situations I can see making the hairpin take up
less vertical space and using whiteout, in other situations I can see it
being rotated to follow the slope of the beam.  In either of these
cases, in order to know if an intersection occurs, the hairpin needs to
know:

a) The cross staff beams that happen during it.
b) The left and right Y-positions of the beams.
c) The left and right X-positions of the beams.
d) Its own left and right X/Y positions.

(a) is currently impossible to calculate in all circumstances, and (c)
would require a code dup.  I think by making these available as
properties, the user can then use this data to fix the problem.  In the
example given in Issue 36, I would personally rotate the stencil
downwards, and this patch would give me all the data necessary to create
an override for Beam #'rotation.

Cheers,
MS



Please review this at http://codereview.appspot.com/4809051/