help-gnu-music
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

text questions


From: David Petrou
Subject: text questions
Date: Sun, 22 Apr 2001 18:55:47 -0400
User-agent: Mutt/1.2.5i

I'd like to move the text on a note around.  Let's say I have
c^"foo".  I'd like to be able to shift "foo" vertically and
horizontally.  After searching the manual for half an hour, I found
(in the regression section) that I can do:

  \property Voice.TextScript \set #'padding = #5

However, this only works in the up-down direction.  I also found that
for \mark stuff, I can do something like:

  \outputproperty #(make-type-checker 'mark-interface) 
  #'extra-offset = #'(-1 . 4)

but haven't found an equivalent for the text over a note.  I don't
care if I use "^" or \mark, but when I tried doing \mark, I got a
bunch of font errors.  (My text actually has a metronome indication in
it.)

Question 2:

I'd like to get the word "Keyboard" as the instrument on a piano
staff.  I have a StaffGroup with 3 staves and 1 piano staff.  I've
tried putting:

            \property PianoStaff.instrument = "Keyboard "

in every possible location within the PianoStaff, but nothing prints.

Comment on the manual: A few weeks ago there was discussion on the
order of topics in the manual.  I think it was Mats that suggested
that things like the definition of engraver, interpretation, contexts,
etc. should go toward the beginning.  Others suggested that just
simple stuff should go at the beginning, leaving the boring stuff at
the end for the reason that most of the time, people won't need to
know what goes on underneath.

I use lily regularly and often spend a _lot_ of time trying to get
information from the manual because in almost everything I do, I need
to tweak something, that is, to make a special case adjustment.  If
I'm not alone on this, then maybe it's a good idea to have a thorough
explanation of all the terminology and concepts at the beginning of
the manual, so that if the user studies those sections, he or she will
be able to figure out 90% of these tweaks on his own.  As it stands
now, I find many of the answers to what I want to do by grep'ing
around the input/ directory.

david



reply via email to

[Prev in Thread] Current Thread [Next in Thread]