bug-lilypond
[Top][All Lists]
Advanced

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

Re: after \once \set fingeringOrien tations… Lilypond falls back to #up


From: -Eluze
Subject: Re: after \once \set fingeringOrien tations… Lilypond falls back to #up
Date: Mon, 4 Jul 2011 14:17:03 -0700 (PDT)


Dmytro O. Redchuk-2 wrote:
> 
> pps. Let's continue with "\once \set" issue.
> 
sure - i'll try to summarize:


\set deals with context properties
\override deals with grob properties
\override stacks the previous settings and recalls them when \once is used
\revert falls back to the "original" settings (whatever this means)
\set does not stack the previous (changed) settings so it does not fall back
on those when \once is used
\unset falls back to the original settings as well


 

now there is a problem when you define your own context properties:

fingeringOrientations are defined at the \Score level; even if you define a
different list in the \voice level, after a \unset or \once \set the
fallback will go to the original \Score definitions.

this is not very helpful when you write guitar notes which often need 3 (or
even more) polyphonic voices:

often you will put the bass, discant and the notes between into three
different voices and use a different fingering policy for each: the bass
gets the fingering below, the discant above and the notes between are
fingered on the left (or right). you can define this in a \with or \layout
{\context … }command

sometimes you have to change this policy (there are many reasons for such a
temporary change) - that's life (or music)!

and that's where the lack of stacking the previous settings becomes
disastrous: you have to redefine what you thought was defined for the rest
of the voice; what you had defined for the voice is overridden and has gone.

the \once becomes some kind of "shortcut" for "\set it for the next
espression and then forget all the previous settings" - except for the high
level definition.

 

hope this does not sound to pessimistic but shows what is needed from a
practical view. i wouldn't qualify the actual situation as buggy but
certainly worth to be thought over, documented or even changed!

in any case - if i missed something please let me know!

cheers

Eluze



-- 
View this message in context: 
http://old.nabble.com/after-%5Conce-%5Cset-fingeringOrientations%E2%80%A6-Lilypond-falls-back-to--up-tp31987692p31992608.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.


reply via email to

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