[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: break-visibility of KeySignature and KeyCancellation inconsistent
From: |
Thomas Morley |
Subject: |
Re: break-visibility of KeySignature and KeyCancellation inconsistent |
Date: |
Mon, 26 Aug 2019 11:10:18 +0200 |
Am Sa., 17. Aug. 2019 um 18:17 Uhr schrieb Malte Meyn <address@hidden>:
>
> Hi list,
>
> I wonder why there is two different ways to change the break-visibility
> of KeySignature and KeyCancellation grobs:
>
> %%%%%%%%%%%%%%%%%%%%%%%%%%%
> \version "2.21.0"
>
> {
> \set Staff.explicitKeySignatureVisibility = #end-of-line-invisible
> \override Staff.KeyCancellation.break-visibility = #end-of-line-invisible
> \key g \major
> R1
> \break \key f \major
> R
> }
> %%%%%%%%%%%%%%%%%%%%%%%%%%%
>
> \overriding KeySignature.break-visibility has no effect and there is no
> context property explicitKeyCancellationVisibility, however there is
> printKeyCancellation which is a boolean, not a boolean vector. That’s
> inconsistent and I cannot imagine why this would be necessary. I
> searched the tracker and the mailing list archives but I couldn’t find
> any hints … Should we consider this a bug?
>
> Cheers,
> Malte
Hi Malte,
I stumbled across it as well.
Though I seem to remember there was a reason for it, but can't find a
link to the discussion anymore.
So I even can't say whether it was a _good_ reason...
Sorry to be of not more help,
Harm