[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Potential issue 39 fix w/ patch
From: |
Mike Solomon |
Subject: |
Re: Potential issue 39 fix w/ patch |
Date: |
Thu, 6 Jan 2011 12:45:31 -0500 |
Thanks Keith,
I'm sure that you can change stem length at that point in the code.
I'll put together something and send it out.
I don't mind the horizontal shift, as simultaneous notes are always
horizontally shifted if they are the same notable near neighbors. The problem
arises when it causes ambiguity in the rhythm.
Anyway, I'll get on your suggestion and will leave it to others to decide which
one is prettier. In neither case would the solution be very computationally
expensive.
Cheers,
Mike
On Jan 5, 2011, at 23:49, Keith OHara <address@hidden> wrote:
> Mike Solomon <mikesol <at> ufl.edu> writes:
>> I've included before and after photos.
>
> Hi Mike.
> The hemidemisemiquaver(*) and the minim are supposed to be simultaneous, so I
> do not like the horizontal shift.
>
> There is no mention in issue 39 of the desired output. The only thing I can
> imagine wanting done automatically is lengthening the stem. Is it too late
> for
> that when note-collisions are being handled?
>
> If the best achievable output is only slightly more preferable than the
> collision, but costs significant computation for every note-collision, we
> might
> want to simply note this one as 'not worth fixing with the methods tried so
> far'.
>
> I'll still try your patch.
> --
> Keith
>
> [*] I'm American, actually, so would normally say 64th note; I just like the
> cheap thrill I get out of writing hemidemisemiquaver.
>
>
>
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-devel