Le 21/12/2021 à 22:29, David Kastrup a écrit :
Jean Abou Samra writes:
[Valentin]
Hello Jean, hello David, hello Kieren,
you should even be able to write (if sten (ly:stencil-extent sten)),
as the stencil should always be a stencil or #f.
The two universally accepted values for any prop
Hi Valentin
You're right. Having read your latest a few times, I see that it is,
indeed, not very complicated. Thanks for the clarification.
David
On Tue, 2021-12-21 at 00:26 +0100, Valentin Petzel wrote:
> Hello David,
> It’s not very complicated: The old behaviour uses one Mark_engraver
> t
Sorry, It was my mistake, I was confusing what of my own code I was trying it
on.
> 21 dec. 2021 kl. 09:03 skrev Jean Abou Samra :
>
> Le 21/12/2021 à 00:12, Leo Correia de Verdier a écrit :
>> Thanks a lot!
>>
>> It’s a perfect solution for the typesetting, but I wonder if it would be
>> poss
Jean Abou Samra writes:
> [Valentin]
>> Hello Jean, hello David, hello Kieren,
>>
>> you should even be able to write (if sten (ly:stencil-extent sten)),
>> as the stencil should always be a stencil or #f.
>
>
> The two universally accepted values for any property
> regardless of the predicate ar
Le 21/12/2021 à 21:49, David Kastrup a écrit :
Your "if" has no else path. Maybe replace it with "and", assuming that
ChordName knows how to deal with an X-offset of #f (which tends to be a
valid setting for any predicate in grob properties).
Ouch. Looking at the relevant code path uncovered
Hello David,
using and here is a fancy way of doing things, that is true. Best way would
probably to use a suitable else value like '(0 . 0) or something, I guess.
Cheers,
Valentin
21.12.2021 21:58:59 David Kastrup :
> Valentin Petzel writes:
>
>> Hello Jean, hello David, hello Kieren,
>>
>
Valentin Petzel writes:
> Hello Jean, hello David, hello Kieren,
>
> you should even be able to write (if sten (ly:stencil-extent sten)),
> as the stencil should always be a stencil or #f.
The return value will still be neither #f nor a dimension unless you
replace "if" with "and".
--
David Ka
Hello Jean, hello David, hello Kieren,
you should even be able to write (if sten (ly:stencil-extent sten)), as the
stencil should always be a stencil or #f.
Cheers,
Valentin
21.12.2021 21:42:13 Jean Abou Samra :
> Le 21/12/2021 à 21:33, David Kastrup a écrit :
>> Kieren MacMillan writes:
>>>
Jean Abou Samra writes:
> Certainly. Kieren, try this:
>
> \version "2.22.1"
>
> \layout { ragged-right = ##f }
>
> music = \chordmode {
> c1 c:7 c:m7 c':m6.4.2/ees \once \omit ChordName c
> }
>
> \score {
> <<
> \new ChordNames \music
> \new Staff \music
> >>
> \layout {
> \c
Hi all,
>>> Any thoughts about what might be going wrong?
>> It is applied to a grob that has been given the \omit treatment?
> Certainly. Kieren, try this
Perfection!
Thank you, Aaron and David and Jean!
Onward and upward. =)
Kieren
Le 21/12/2021 à 21:33, David Kastrup a écrit :
Kieren MacMillan writes:
Hi again,
When I try to use it in my main file, I get this:
In procedure ly:stencil-extent in expression (ly:stencil-extent sten X):
/Users/kmac/Documents/01_music/scores/_include/paper/musical.ily:254:21:
Wrong type ar
Kieren MacMillan writes:
> Hi again,
>
> When I try to use it in my main file, I get this:
>
> In procedure ly:stencil-extent in expression (ly:stencil-extent sten X):
> /Users/kmac/Documents/01_music/scores/_include/paper/musical.ily:254:21:
> Wrong type argument in position 1 (expecting Stenci
Hi again,
When I try to use it in my main file, I get this:
In procedure ly:stencil-extent in expression (ly:stencil-extent sten X):
/Users/kmac/Documents/01_music/scores/_include/paper/musical.ily:254:21: Wrong
type argument in position 1 (expecting Stencil): #f
Any thoughts about what might
Hi Aaron,
> I've used something like this in the past
That's great! I just wrapped your 'center-er' in a (max -2 etc), and it's
exactly what I want:
\version "2.22.0"
\layout { ragged-right = ##f }
music = \chordmode {
c1 c:7 c:m7 c':m6.4.2/ees
}
\score {
<<
\new ChordNames \mus
On 2021-12-21 10:30 am, Kieren MacMillan wrote:
and am once again in need this ChordName alignment feature. Is anyone
out there able to shepherd me through building a callback to make this
happen?
I've used something like this in the past:
\version "2.22.0"
music = \chordmode {
\overri
oops! forgot the ** footnote:
** Thanks again to the ’Pond for how amazing the app already is: every time I
crank out amazing looking scores and parts in such a short period of time, I'm
reminded how lucky we all are for the efforts of the developers. All of my
Finale- and Sibelius-using friend
Hi all,
I'm cramming out scores for an upcoming workshop of a new musical**, and am
once again in need this ChordName alignment feature. Is anyone out there able
to shepherd me through building a callback to make this happen?
Thanks,
Kieren.
> On Jun 16, 2018, at 1:41 PM, Kieren MacMillan
>
Hello Jean,
That is not correct. You’re getting this message because you didn’t specify a
direction for the Script. Basically the default direction of most
articulations depends on the stem direction, and thus the calculation of the
direction requires the presence of a proper direction-source,
Le 21/12/2021 à 00:12, Leo Correia de Verdier a écrit :
Thanks a lot!
It’s a perfect solution for the typesetting, but I wonder if it would be
possible to process them earlier, so I could have them work with the articulate
script or at least consistently affect midi playback.
It may well be
Le 21/12/2021 à 01:20, Valentin Petzel a écrit :
Hello Jean!
That is a nice solution, but it has some issues. For one thing this will case
problem if we have a Script on a skip that is used for something like spacing
a markup (resulting in a compile error if a skip has both a script and for
exam
20 matches
Mail list logo
