[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-user
Subject:    Re: \oneVoice and \voiceXX commands having the wrong scope
From:       "Yuval Harel" <yuvalh () hotpop ! com>
Date:       2005-01-26 0:25:32
Message-ID: opsk6osufe0qq1lr () uvpc
[Download RAW message or body]

\oneVoice scope too short:
==========================

\version "2.4.2"

\new Staff {
	\clef bass
	\context Voice="1" {
		\oneVoice
		c'2-\markup {\column < "oneVoice" "(This markup generates a programming  
error)">} r2 |
		<< {b2-"Polyphony" r2} \\ {g2 r2} >>
		c'2-"oneVoice should still be in effect here." r2 |
	} |
}

\voiceOne scope too long:
=========================

\version "2.4.2"

\new Staff {
	\clef bass
	c'2 r2	|	% commenting out this line eliminates the problem
	<< {\voiceOne r1-"voiceOne"} >> |
	c'2-"voiceOne is still in effect" r2
	\oneVoice
	r1-\markup {\column <"oneVoice" "(This markup generates a programming  
error)">} |
}

On Wed, 26 Jan 2005 00:22:14 +0100, Erik Sandberg  
<erik.sandberg.9195@student.uu.se> wrote:

> On Tuesday 25 January 2005 15.03, Yuval Harel wrote:
>> Hi,
>>
>> I found that \oneVoice and \voiceOne sometimes have unexpected effects.
>> Here are two examples which might be two separate bugs.
>> When preparing the examples I also noticed that adding markup can
>> sometimes generate programming errors in these
>> situations.
>
> The mailing list strips attachments. Could you please resend it, pasted  
> into
> the message?
>
> Erik
>







[prev in list] [next in list] [prev in thread] [next in thread]