Carl, thanks for your verbose explanation. This helps understanding
Lilypond "under the hood" more and more!
Stephan
Am 17.05.2022 um 21:58 schrieb Carl Sorensen:
On Tue, May 17, 2022 at 1:26 PM Stephan Schöll wrote:
Hi all
My impression that the mailing list has long delays somewh
Thanks,
No comment on the documentation. The fault is on me because I only looked
at the internals of the Clef and not the Clef Modifier which was literally
the next chapter.
It's one of those things I rarely use so I hadn't looked thoroughly at
those specific chapters.
On Wed, May 18, 2022 at
Good morning,
I really appreciate your solutions and I'm trying to impress box only on
some systems of the score.
So I'm trying to do something like \once \override Score.System.stencil =
...
But there is no response. I've tried also with \overrideProperty, but
nothing happens.
Do you have any advi
Le 18/05/2022 à 15:44, Rip _Mus a écrit :
Good morning,
I really appreciate your solutions and I'm trying to impress box only
on some systems of the score.
So I'm trying to do something like \once \override
Score.System.stencil = ...
But there is no response. I've tried also with \overridePrope
Le 18/05/2022 à 16:02, Jean Abou Samra a écrit :
You could use \alterBroken if it supported callbacks, but it doesn't
(well, they may or may not work or work partially depending on internal
details)
OK,
https://gitlab.com/lilypond/lilypond/-/merge_requests/1369
Jean is correct in telling you why your approach does not work. The system is
not something that is created in a certain timestep, but rather as a single
grob at the begin of translation and then broken down afterward, basically
copying the properties of the original System grob.
However while
Le 18/05/2022 à 17:56, Valentin Petzel a écrit :
Jean is correct in telling you why your approach does not work. The system is
not something that is created in a certain timestep, but rather as a single
grob at the begin of translation and then broken down afterward, basically
copying the propert
Valentin Petzel writes:
> Jean is correct in telling you why your approach does not work. The
> system is not something that is created in a certain timestep, but
> rather as a single grob at the begin of translation and then broken
> down afterward, basically copying the properties of the origin
Le 18/05/2022 à 22:37, David Kastrup a écrit :
Valentin Petzel writes:
Jean is correct in telling you why your approach does not work. The
system is not something that is created in a certain timestep, but
rather as a single grob at the begin of translation and then broken
down afterward, basi
Le 18/05/2022 à 23:58, Jean Abou Samra a écrit :
(say)
\overrideMidBrokenSpanner Context.Grob.property = ...
Actually, the ideal interface for this is probably a modifier
like \once, \temporary and \single.
\broken \override Context.Grob.property = ...
Jean Abou Samra writes:
> Le 18/05/2022 à 23:58, Jean Abou Samra a écrit :
>> (say)
>> \overrideMidBrokenSpanner Context.Grob.property = ...
>
>
> Actually, the ideal interface for this is probably a modifier
> like \once, \temporary and \single.
>
> \broken \override Context.Grob.property = .
Le 19/05/2022 à 00:56, David Kastrup a écrit :
Jean Abou Samra writes:
Le 18/05/2022 à 23:58, Jean Abou Samra a écrit :
(say)
\overrideMidBrokenSpanner Context.Grob.property = ...
Actually, the ideal interface for this is probably a modifier
like \once, \temporary and \single.
\bro
Jean Abou Samra writes:
> Le 19/05/2022 à 00:56, David Kastrup a écrit :
>> Jean Abou Samra writes:
>>
>>> Le 18/05/2022 à 23:58, Jean Abou Samra a écrit :
(say)
\overrideMidBrokenSpanner Context.Grob.property = ...
>>>
>>> Actually, the ideal interface for this is probably a modifie
Hello,
When I have a beamed tuplet (without a bracket) and a fingering on one
note, the TupletNumber moves outward from the staff despite there being no
possibility of a collison. In normal usage, TupletNumber should stay as
close as possible to the beam.
Example:
\version "2.22.2"
\relative c
{
14 matches
Mail list logo
