On Thu, Oct 7, 2010 at 5:12 PM, Patrick McCarty <pnor...@gmail.com> wrote:
> On Wed, Oct 6, 2010 at 10:14 AM, Carl Sorensen <c_soren...@byu.edu> wrote:
>>
>> On 10/5/10 11:44 PM, "David Kastrup" <d...@gnu.org> wrote:
>>>
>>> I think a revert would be more appropriate.
>>
>> I agree that a revert would be more appropriate. However, a revert would
>> be very difficult to accomplish, because there is no easy way to save the
>> "original" value. The value is only known in the translation stage as a
>> context property, so we can't really save the value for use in the parsing
>> stage.
>>
>> Right now, the benefit/time ration isn't high enough for me to code the
>> revert.
>>
>> I'm fine to have an enhancement request to implement it as a revert,
>> however.
>
> Can't we just use \unset instead? Like
>
> diff --git a/ly/property-init.ly b/ly/property-init.ly
> index 5724004..9f7876d 100644
> --- a/ly/property-init.ly
> +++ b/ly/property-init.ly
> @@ -101,7 +101,7 @@ cadenzaOn = {
> cadenzaOff = {
> \set Timing.timing = ##t
> \set Timing.measurePosition = #ZERO-MOMENT
> - \set Timing.autoBeaming = ##t
> + \unset Timing.autoBeaming
> }
Hmm, after testing a little more, that didn't work as I expected it
to. I don't use \unset very often.
Thanks,
Patrick
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
