Re: Quanting and issue 37

[Mike Solomon]

Answered my own question...new patch attached that does collision management 
before quanting and then does correct quanting.
First one who throws it up on Rietveld wins!

0008-Reorders-code-to-get-the-quanting-in-after-the-colli.patch
Description: Binary data

0007-Format-fixes-cleaner-code-better-name-more-intellige.patch
Description: Binary data

0006-Better-reflects-what-is-actually-under-the-beam.patch
Description: Binary data

0005-Attempt-to-deal-with-smaller-font-sizes-like-cue-not.patch
Description: Binary data

0004-Changes-suggested-by-Carl.patch
Description: Binary data

0003-Intermediary-37-patch.patch
Description: Binary data

0002-Fixes-formatting-problems.patch
Description: Binary data

0001-Fixing-issue-37-with-extra-position-callback.patch
Description: Binary data

Cheers,
MS
On Jan 24, 2011, at 6:49 AM, address@hidden wrote:

> Hey all,
> 
> I am trying to understand beam-quanting.cc better, and I think I know how I'm 
> gonna tackle this.
> 
> I'm going to put my collision callback before beam quanting, and then try 
> something to the effect of:
> 
> if (the beam was pushed up during the collision callback)
>  impose an insanely prohibitive demerit for the beam position going down in 
> the quanting
> else if (the beam was pushed down during the collision callback)
>  impose an insanely prohibitive demerit for the beam position going up in the 
> quanting
> 
> Could anyone give me a quick primer on how to do that?
> 
> Cheers,
> MS
> 
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-devel