[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 2.16 release candidate 3 imminent

From: Carl Sorensen
Subject: Re: 2.16 release candidate 3 imminent
Date: Sat, 21 Jan 2012 18:24:05 +0000
User-agent: Microsoft-MacOutlook/

On 1/21/12 11:16 AM, "David Kastrup" <address@hidden> wrote:

>Carl Sorensen <address@hidden> writes:
>> On 1/21/12 10:37 AM, "David Kastrup" <address@hidden> wrote:
>>>I have actually found out that I promised too much about string numbers
>>>appearing on isolated notes: since the string number events _are_
>>>listened to (likely by the tabstaff engraver team), the rhythmic music
>>>iterator _does_ broadcast them instead of leaving them as articulations.
>> The tabstaff engraver team listens to *both* string number events *and*
>> articulations. Combining the two is a bit of a pain.
>If nobody listens to string number events, they will stay articulations
>except when placed explicitly on chords like <c>\3 and then you deserve
>what you don't get.
>> That's why I asked earlier to get some consistency.  If we can get
>> string number events to always be in articulations, we don't need to
>> broadcast string number events.  If the rhythmic music iterator can
>> make them always show up as articulations, that would be great.
>That would be the case.

Great!  I'll make tabstaff engraver stop listening to string number events
once your patch is pushed.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]