Re: Moving a Clef bellow notes in other Staff to save horizontal space?

[Stefano Troncaro]

Lol, that's what I get for dealing with this stuff before going to sleep. I realized of my mistake after turning off the computer and laughed at the situation. I never doubted that someone would point out my stupidity.

El jue., 9 may. 2019 a las 2:52, David Kastrup (<address@hidden>) escribió:

Stefano Troncaro <address@hidden> writes:

> Hi Kieren, that's great! It works wonderfully.
>
> I experimented a bit with your idea, the same result can be achieved with
> just \once \override Staff.Clef.X-extent = #'(.7 . 2.2)
> It looks like by changing the first number of the pair one can be very
> precise about how much the Clef goes bellow the notes, while the other
> determines the distance between the Clef and the BarLine. Since X-extent is
> a pair it can't be offset,

Come again?

    File: lilypond-notation.info,  Node: The offset command,  Next: Modifying alists,  Prev: set versus override,  Up: Modifying properties

    5.3.6 The ‘\offset’ command
    ---------------------------

    While it is possible to set grob properties to new values with the
    ‘\override’, ‘\tweak’, and ‘\overrideProperty’ commands, it is often
    more convenient to modify such properties relative to a default value.
    The ‘\offset’ command is available for this purpose.

       The syntax for ‘\offset’ is

         [-]\offset PROPERTY OFFSETS ITEM

[...]

    Properties which may be offset
    ..............................

[...]

       The following criteria determine whether a property can be modified
    with ‘\offset’:

[...]

       • The property takes a numerical value.  Numerical values include
         ‘number’, list of ‘number’s, ‘number-pair’, and ‘number-pair-list’.
         The pages at *note (lilypond-internals)All layout objects:: list
         the type of data characteristic to each property.  It is immaterial
         whether the default setting is a function.


--
David Kastrup