>> Since I don't have experience with chord names I ask users who need
>> this feature to check whether it works as expected in general.
>
> It works like a charm in my source! Thanks for researching this.
:-)
https://gitlab.com/lilypond/lilypond/-/merge_requests/2281
Werner
On Thu, Mar 21, 2024 at 2:30 PM Werner LEMBERG wrote:
>
> I think I've found the real fix for the problem. Suddenly remembering
> that we already have the `Span_bar_stub_engraver` to handle exactly
> such situations I wondered why it works for lyrics but not for chord
> names. Comparing the
>>> I remembered that you can add the Bar_engraver to ChordNames.
>>> Making them transparent so they do not visually interfere with the
>>> SpanBar, but they still take up space.
>>
>> Nice! This begs the question whether we have a real bug or 'just'
>> insufficient documentation...
>
> I was
On Wed, Mar 20, 2024 at 8:54 AM Aaron Hill wrote:
> Oh, I think I found another option:
>
>
> \version "2.25.13"
>
> #(ly:set-option 'debug-skylines #t)
> \layout {
>\context { \Score
> \override NonMusicalPaperColumn.show-horizontal-skylines = ##t
>}
>\context {
On 2024-03-20 9:01 am, Werner LEMBERG wrote:
I remembered that you can add the Bar_engraver to ChordNames.
Making them transparent so they do not visually interfere with the
SpanBar, but they still take up space.
Nice! This begs the question whether we have a real bug or 'just'
insufficient
> Oh, I think I found another option:
>
>
> \version "2.25.13"
>
> #(ly:set-option 'debug-skylines #t)
> \layout {
> \context { \Score
> \override NonMusicalPaperColumn.show-horizontal-skylines = ##t
> }
> \context { \ChordNames
> \consists "Bar_engraver"
> \override
On 2024-03-20 8:14 am, Knute Snortum wrote:
Ah, I see this is just for debugging. Thank you. Your solution helps
when
put into my bigger project. Some -- but not all -- of the bars are now
wide enough.
Oh, I think I found another option:
\version "2.25.13"
#(ly:set-option
On Wed, Mar 20, 2024 at 8:01 AM Aaron Hill wrote:
> ly:separation-item::print no longer exists, as all grobs support the
> properties show-horizontal-skylines and show-vertical-skylines.
>
> So, swap out that \override with:
>
>
>\override NonMusicalPaperColumn.show-horizontal-skylines
On 2024-03-20 8:07 am, Jean Abou Samra wrote:
Le mercredi 20 mars 2024 à 15:56 +0100, Jean Abou Samra a écrit :
Le mercredi 20 mars 2024 à 07:51 -0700, Knute Snortum a écrit :
> Your solution requires version 2.22 and I'm using 2.24
> (with the \alternative command so it's not easy to change)
On Wed, Mar 20, 2024 at 8:07 AM Jean Abou Samra wrote:
> Le mercredi 20 mars 2024 à 15:56 +0100, Jean Abou Samra a écrit :
> > Le mercredi 20 mars 2024 à 07:51 -0700, Knute Snortum a écrit :
> > > Your solution requires version 2.22 and I'm using 2.24
> > > (with the \alternative command so it's
Le mercredi 20 mars 2024 à 15:56 +0100, Jean Abou Samra a écrit :
> Le mercredi 20 mars 2024 à 07:51 -0700, Knute Snortum a écrit :
> > Your solution requires version 2.22 and I'm using 2.24
> > (with the \alternative command so it's not easy to change)
>
> The old \alternative syntax is still
On 2024-03-20 7:51 am, Knute Snortum wrote:
Thank you so much for this fix and for entering an issue! There is
just
one thing that is a problem for me. Your solution requires version
2.22
and I'm using 2.24 (with the \alternative command so it's not easy to
change). When I your solution
Le mercredi 20 mars 2024 à 07:51 -0700, Knute Snortum a écrit :
> Your solution requires version 2.22 and I'm using 2.24
> (with the \alternative command so it's not easy to change)
The old \alternative syntax is still supported in 2.24.
signature.asc
Description: This is a digitally signed
On Tue, Mar 19, 2024 at 4:34 PM Aaron Hill wrote:
> ...
>
> Curious. The skylines look interesting, almost like the SpanBar is not
> being factored in, only the parts of the BarLine.
>
> Below, I attempted to add some virtual height to the ChordName, and it
> seemed to allow the ChordName to
>> Aaron, please file an issue, referring to this e-mail thread.
>
> First time creating an issue, so hopefully this is up to snuff.
Thanks a lot!
> Added: https://gitlab.com/lilypond/lilypond/-/issues/6703
>
> By the by, I do not appear to have permissions for setting labels,
> but I think
On 2024-03-20 1:45 am, Werner LEMBERG wrote:
In some situations, chord names collide with the span bar of a
Grand or Piano Staff. Here is an example: [...]
[...] Still sounds like a defect of some sort, as the default
behavior should probably be handling things.
Aaron, please file an issue
>> In some situations, chord names collide with the span bar of a
>> Grand or Piano Staff. Here is an example: [...]
>
> [...] Still sounds like a defect of some sort, as the default
> behavior should probably be handling things.
Aaron, please file an issue, referring
On 2024-03-19 2:29 pm, Knute Snortum wrote:
I ran into something today -- it's not quite a bug; more of an "ugly."
In
some situations, chord names collide with the span bar of a Grand or
Piano
Staff. Here is an example:
\version "2.25.13"
\score {
\new GrandSta
I ran into something today -- it's not quite a bug; more of an "ugly." In
some situations, chord names collide with the span bar of a Grand or Piano
Staff. Here is an example:
\version "2.25.13"
\score {
\new GrandStaff <<
\new Staff \relative { c''4 c c c | c c
19 matches
Mail list logo
