On Sat, Jan 25, 2020 at 3:05 PM Aaron Hill wrote:
> On 2020-01-24 9:12 am, Paolo Prete wrote:
> > I'm trying to implement the work-around you suggested.
> > TupletNumber doesn't cause the discussed weird space.
> >
> nstead, simply replace the normal stencil procedure
>
On 2020-01-24 9:12 am, Paolo Prete wrote:
I'm trying to implement the work-around you suggested.
TupletNumber doesn't cause the discussed weird space.
However, this weird space happens as soon as I access the stencil (or
any
property of it) of the TupletBracket grob
Then, even if I get the
On Wed, Jan 22, 2020 at 11:56 PM Aaron Hill
wrote:
> On 2020-01-22 7:26 am, Paolo Prete wrote:
> > The problem is associated with:
> >
> > https://lists.gnu.org/archive/html/lilypond-user/2020-01/msg00467.html
> >
> > Sorry if I insist again with this: is there a fix (or work-around) for
> > it?
Y
>
> All of my helper functions for overlaying stencils are really just
> hacks; they might work for some grobs and fail for others. And when
> things stop working, you just have to look for another hack. For
> instance, if messing with the stencil for TupletBracket is not working,
> perhaps
On 2020-01-22 7:26 am, Paolo Prete wrote:
The problem is associated with:
https://lists.gnu.org/archive/html/lilypond-user/2020-01/msg00467.html
Sorry if I insist again with this: is there a fix (or work-around) for
it?
The function is ***very*** useful, You can really see what happens with
To Aaron (and any other helpful contributor):
As you can see in the below snippet, the visualize-padding function you so
kindly provided, doesn't work in some cases with TupletBracket. Here is a
snippet where the bug occurs.
The problem is associated with:
https://lists.gnu.org/archive/html
