Hi Vaughan,
> Putting the clef where it is a bit idiosyncratic, but it lets me do things
> like have a trombone part use bass clef in the score and tenor clef in the
> part.
Related: I have started to think of "clef" as presentation-layer [as opposed to
content-layer] data. Therefore, as soon
On 23-9-2018 15:49, Kieren MacMillan wrote:
Of course, a lot of it is simply personal preference/style, so there’s no big
need to change if you don’t agree with my reasoning! I was just offering a
possible improvement.
Cheers,
Kieren.
Thanks for explaining. I'll think about it.
On Mon, 24 Sep 2018 at 04:25, Simon Albrecht wrote:
> On 18.09.2018 21:10, Kieren MacMillan wrote:
> > Here’s one way. (Note that I also <<>>'ed the \global variable into
> each*staff* context in the score, rather than into each note variable
> definition; personally, I think that is better
On 18.09.2018 21:10, Kieren MacMillan wrote:
Here’s one way. (Note that I also <<>>'ed the \global variable into each*staff*
context in the score, rather than into each note variable definition; personally, I think
that is better coding style, for many reasons.)
I for my part don’t feel
p.s.
>> In the rewrite Kieren gave of Bernhard's score the global variable is still
>> included at the voice level.
And, yes, I would likely move the \global variable to the staff level(s) — or
even score, if the type of global information warranted/allowed — though I
didn’t go that far in my
Hi all,
> In the rewrite Kieren gave of Bernhard's score the global variable is still
> included at the voice level. So, it seems that less typing is not the reason.
No, less typing is not the reason.
Here are three of the more important reasons I prefer late-stage combination:
1. It’s less
On 23-9-2018 08:41, arnepe wrote:
hello Auke,
(/bear with me, I'm not a programmer and may not know the correct
terminology/)
one reason would be that "voice" is a child of "staff": definitions in
"staff" are inherited by "voice",
plus the benefit of less typing...
cheers
Arne
Hello Arne,
hello Auke,
(/bear with me, I'm not a programmer and may not know the correct
terminology/)
one reason would be that "voice" is a child of "staff": definitions in
"staff" are inherited by "voice",
plus the benefit of less typing...
cheers
Arne
--
Sent from:
On 18-9-2018 21:10, Kieren MacMillan wrote:
(Note that I also <<>>'ed the \global variable into each *staff*
context in the score, rather than into each note variable definition;
personally, I think that is better coding style, for many reasons.)
I'm intruiged. What would those 'many
Hi Bernhard,
> Please show me how to deal with different tempo declarations on different
> staves.
Here’s one way. (Note that I also <<>>'ed the \global variable into each
*staff* context in the score, rather than into each note variable definition;
personally, I think that is better coding
I have the following minimal example (from Frescobaldi with some
eliminations). What I cannot achieve is that the
\tempo 4=96
becomes effective on the organpart. It works only with the global
declaration. Removing this, the other tempo declaration are not visible.
Please show me how to deal with
11 matches
Mail list logo
