[EMAIL PROTECTED] writes:
> Thanks, that's much better. Except that the crescendo gets
> completely squashed in
>
> \score {
>
> \notes\relative c'' {
> \property Score.DynamicText \set #'no-spacing-rods = ##f
> \property Score.DynamicText \set #'X-extent = #'(-10 . 20)
> e_\p
Thanks, that's much better. Except that the crescendo gets
completely squashed in
\score {
\notes\relative c'' {
\property Score.DynamicText \set #'no-spacing-rods = ##f
\property Score.DynamicText \set #'X-extent = #'(-10 . 20)
e_\p \> e_\p \!
}
\paper{raggedright =
Maybe your changes haven't made it to the CVS server yet
(my ChangeLog has revision 1.1692).
No matter how I set no-spacing-rods and X-extent, the two p
overlap.
/Mats
Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
I'm sorry, but I cannot see any difference in the output compared to
whe
[EMAIL PROTECTED] writes:
> Maybe your changes haven't made it to the CVS server yet
> (my ChangeLog has revision 1.1692).
> No matter how I set no-spacing-rods and X-extent, the two p
> overlap.
Probably. Please try again now.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.x
[EMAIL PROTECTED] writes:
> I'm sorry, but I cannot see any difference in the output compared to
> when I reported the problem.
try this
\score {
\notes\relative c'' {
\property Score.DynamicText \set #'no-spacing-rods = ##f
\property Score.DynamicText \set #'X-extent = #'(-1 . 2)
I'm sorry, but I cannot see any difference in the output compared to
when I reported the problem.
/Mats
Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
you could try #'no-spacing-rods on DynamicText to force more space, and
if necessary widen it with
DynamicText \set #'X-extent = #(-10 .
[EMAIL PROTECTED] writes:
> >
> > you could try #'no-spacing-rods on DynamicText to force more space, and
> > if necessary widen it with
> >
> >DynamicText \set #'X-extent = #(-10 . 10)
> >
> > or somesuch.
>
> I already tried these, to no avail. See the following example:
I have fixed t
Mats -
It works fine for me, setting #'no-spacing-rods to ##t rather than ##f.
Thanks to both you and Han-Wen for the help.
On Fri, Feb 06, 2004 at 10:16:05AM +0100, Mats Bengtsson wrote:
> It seems Han-Wen was in a hurry, the correct syntax is
> #'(-10 . 10) instead of #(-10 . 10)
> However,
It seems Han-Wen was in a hurry, the correct syntax is
#'(-10 . 10) instead of #(-10 . 10)
However, it didn't seem to have any effect, see
http://mail.gnu.org/archive/html/bug-lilypond/2004-02/msg00047.html
/Mats
Kevin C. Baird wrote:
Hi. Thank you. #'no-spacing-rods helped. I did want to expand
Hi. Thank you. #'no-spacing-rods helped. I did want to expand a bit with
the X-extent widening you suggested 2nd.
Attached is my .ly file and the error output.
On Thu, Feb 05, 2004 at 01:11:28PM +0100, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > Sorry, I plan to learn to read any yea
Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
Sorry, I plan to learn to read any year :-).
I tried some different property settings in a crowded score,
but none of them worked as I expected, so I leave the question
to others who know better.
As a workaround, you could introduce manual line
[EMAIL PROTECTED] writes:
> Sorry, I plan to learn to read any year :-).
>
> I tried some different property settings in a crowded score,
> but none of them worked as I expected, so I leave the question
> to others who know better.
> As a workaround, you could introduce manual line breaks using
>
Sorry, I plan to learn to read any year :-).
I tried some different property settings in a crowded score,
but none of them worked as I expected, so I leave the question
to others who know better.
As a workaround, you could introduce manual line breaks using
\break in lines that look too crowded.
On Tue, Feb 03, 2004 at 10:12:33AM +0100, Mats Bengtsson wrote:
>
>
> Kevin C. Baird wrote:
> >Hello.
> >
[snip]
> >I also find that my dynamic markings collide horizontally. Is there an
> >easy way to mandate more horizontal space when a note has a dynamic
> >marking?
>
> If you search the m
Kevin C. Baird wrote:
Hello.
With Lilypond 2.1.0-2 on Debian Testing, I get all of my stems up
without declaring a direction. What would be the easiest way to get a
more standard stem direction scheme (i.e., in toward the majority of the
staff unless beamed)?
That sounds very strange. You do
Hello.
With Lilypond 2.1.0-2 on Debian Testing, I get all of my stems up
without declaring a direction. What would be the easiest way to get a
more standard stem direction scheme (i.e., in toward the majority of the
staff unless beamed)?
I also find that my dynamic markings collide horizontal
16 matches
Mail list logo
