Hi Dan,
it looks like \Voice starts you off with a copy of the previously
defined
Voice settings. If \Voice is absent, you start from scratch.
The context settings are saved by name. If you do not change the
name,
the modified settings replace the previous settings of the \Voice
On 2009-09-11, at 06:44 , Kieren MacMillan wrote:
Now my question is... does the order of the lines matter at all? I'm
assuming they do — e.g., if you don't change the \name until after
changing some \override, there'll be confusion — but does anyone
know for certain what the precedence
On 2009-09-09, at 08:59 , Kieren MacMillan wrote:
Hi Dan, Neil, et al.:
Does the following help?
SoloVoice is a kind of Voice. UpperVoice and LowerVoice are kinds
of SoloVoice.
That's [relatively] self-evident. What isn't crystal clear — either
in my mind, or (IMO) in the documentation
Hi Dan, Neil, et al.:
Does the following help?
SoloVoice is a kind of Voice. UpperVoice and LowerVoice are kinds
of SoloVoice.
That's [relatively] self-evident. What isn't crystal clear — either
in my mind, or (IMO) in the documentation — is why the following
wouldn't work (or, perhaps
Hi all,
Let's say I want to create a new subclass of the Staff context called
MyStaff, and the only thing it does is override the InstrumentName
settings. Do I really have to include all the \consists from engraver-
init.ly? i.e., do I really have to use
\context {
\type
2009/9/8 Kieren MacMillan kieren_macmil...@sympatico.ca:
Is there anything like this? (From what I've read and experienced, \alias
does *NOT* do this.)
Have you looked at engraver-init.ly? It should give you an idea how
this works (see the definition for PianoStaff).
Here's a quick snippet
On 2009-09-08, at 15:25 , Kieren MacMillan wrote:
It would be so much easier to be able to force inheritance of
everything, e.g.
\context {
\name MyStaff
\from Staff
instrumentName = #MyStaff
shortInstrumentName = #My
}
Is there anything like this? (From what I've read and
