Am 12. Dezember 2016 13:55:39 MEZ, schrieb Alexander Kobel <a-ko...@a-kobel.de>:
>On 2016-12-12 13:42, Urs Liska wrote:
>> [...]
>>>> BTW: Has this warning been disabled somewhere in the unstable
>>> versions?
>>>> From 2.19.49, I get no complaint even for
>>>> << { \stemDown b' } \\ a' >>
>>>> which clearly collides...
>>
>> I think in this example there actually is no colliding-note-column
>clash because the two note heads don't share the nite column.
>> This is different from visual collisions that should of course be
>avoided.
>
>Hm. But does this mean that a "colliding-note-column clash" is merely a
>
>self-assertion for Lily that it properly positions the heads of a
>chord,
>or a check that applies when a user tweaks the position of a specific
>head? Is that really intended?
I think it had been intended as a warning to the user because two notes in
different voices on the same note column are an indication that there may be
something wrong with the voicing.
>
>And how could I actually produce such a collision? Even { <c' c' d'> }
>doesn't issue a warning...
{
<< { \voiceOne c'' } \\ { \voiceOne c'} >>
}
would probably cause that warning. But for some reason this warning has been
removed recently. (So check with 2.18)
Best
Urs
>
>
>Cheers,
>Alexander
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
