lilypond-user
[Top][All Lists]
Advanced

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

Re: Change direction of already positioned markup?


From: Vaughan McAlley
Subject: Re: Change direction of already positioned markup?
Date: Mon, 1 Jun 2015 23:50:03 +1000

On 1 June 2015 at 12:14, Peter Crighton <address@hidden> wrote:
>
> 2015-05-31 23:43 GMT+02:00 Simon Albrecht <address@hidden>:
>>
>> Am 31.05.2015 um 18:25 schrieb Jacques Menu:
>>
>> Hello Peter,
>>
>> Maybe tags would be an easy solution, specifying variants according to the 
>> uses of the music, i.e. inside an instrument part or inside a full score.
>>
>> What do you think?
>>
>> Probably tags contradict hardcore content/presentation separation :-)
>
>
>
> Exactly. I could use tags and maybe I will in the end. But I would very much 
> like to strictly separate content & presentation.
>
> For now, I can use a voice, which I use for inserting rehearsal marks, to add 
> the markup below the staff and remove it from the other voice:
>
> \editionMod cello 17 0/1 cello.Voice.A _\divisiaIII
> \editionMod cello 17 0/1 cello.Voice.B \once \omit TextScript
>
>
> --
> Peter Crighton | Musician & Music Engraver based in Mainz, Germany
> http://www.petercrighton.de
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>

I’ve been thinking about relying less on tags for better
content/presentation separation. This code seems to work. The variable
isScore will only be evaluated once, during the definition of
divisiaIII.

\version "2.18.2"

% This would appear early in the score or parts files, before
% \include-ing all the music data. This ensures isScore is
% defined where it needs to be.

isScore = ##f % Set to true move directions upward

divisiaIII = \tweak direction #(if isScore UP DOWN) -\markup { "div. a 3" }

{ a1 \divisiaIII }


Vaughan



reply via email to

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