lilypond-devel
[Top][All Lists]
Advanced

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

Re: 2.16 release candidate 3 imminent


From: Marc Hohl
Subject: Re: 2.16 release candidate 3 imminent
Date: Sat, 21 Jan 2012 19:32:16 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111109 Thunderbird/3.1.16

Am 21.01.2012 18:44, schrieb Carl Sorensen:
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.

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.
I must admit that I am lost here and do not quite understand what's going on,
but will there be any difference between

< c\3 e\2 g\1 > and < c e g >\3\2\1

once these changes are implemented?

The former displays circled string numbers in a normal staff,
whereas the latter doesn't. Tablature staffs are identical, of course.

Marc



reply via email to

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