Fix #943.

Fix #943.

See: http://code.google.com/p/lilypond/issues/detail?id=943

- Currently, slur direction is calculated once and possibly modified
  later.  Combine these routines into a single function.

- Check for a post-line-break slur first; in this case, the direction
  should come from the pre-line-break slur.

- Check for a pre-line-break slur next; if found, forward its direction
  to the corresponding post-line-break slur.

- If these conditions do not hold, we have an unbroken slur, so simply
  calculate its direction.

[Neil Puttock, 2010-04-29 22:40:10]

LGTM.

http://codereview.appspot.com/956051/diff/1/3
File lily/slur-scoring.cc (right):

http://codereview.appspot.com/956051/diff/1/3#newcode86
lily/slur-scoring.cc:86: Slur_score_state::slur_direction (Grob *me) const
Do you need to pass `me' here?  Isn't it the same as slur_?

[Patrick McCarty, 2010-04-30 03:22:27]

http://codereview.appspot.com/956051/diff/1/3
File lily/slur-scoring.cc (right):

http://codereview.appspot.com/956051/diff/1/3#newcode86
lily/slur-scoring.cc:86: Slur_score_state::slur_direction (Grob *me) const
On 2010/04/29 22:40:10, Neil Puttock wrote:
> Do you need to pass `me' here?  Isn't it the same as slur_?

Oh yes, thanks for the catch.  I'll amend that and push.