Of course, reserved space, that was the problem :-S
Thanks to you both!
@Mats, is it correct that objects, once 'switched off' with #'stencil =
##f, can't be switched on anymore?
When I try, I get:
warning: type check for `stencil' failed; value `#t' must be of type
`unknown'
Oscar
On Tue, 2008-03-18 at 22:12 +0100, Mats Bengtsson wrote:
> Quoting Marc Hohl <[EMAIL PROTECTED]>:
>
> > On Tuesday 18 March 2008 18:38:59 Oscar van Eijk wrote:
> ...
> > It looks great, the arrows are much better than \rtoe/\ltoe, but
> > there is some
> > small problem left. You blanked the tuplets, but it looks as lilypond
> > reserves the space for the tuplet number - look at bars 3 and 4.
> > A simple and probably sufficient workaround is the command
> > \tupletDown. I put it in your definition
> >
> > tupletsOff = {
> > \tupletDown
> > \override TupletNumber #'transparent = ##t
> > \override TupletBracket #'transparent = ##t
> > }
>
> Well, a much better solution is described in
> http://lsr.dsi.unimi.it/LSR/Item?id=337
> for tuplet brackets in particular and in
> http://lilypond.org/doc/v2.11/Documentation/user/lilypond-learning/Visibility-and-color-of-objects#Visibility-and-color-of-objects
> for any object (such as a TupletNumber) in general (what I have in mind
> is \override TupletNumber #'stencil = ##f ).
>
> /Mats
>
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
