`extroversion' specifies where on the specified polygon to draw with the
pen of the given thickness. Its default of -1 corresponds to the
previous behavior of drawing strictly inside of the given polygon. An
extroversion value of 0 draws exactly along the given polygon, and a
value of 1 will draw just outside of the given polygon.
David Kastrup [Wed, 23 Sep 2015 19:50:39 +0000 (21:50 +0200)]
Issue 4618: Correct argument handling of Unpure_pure_call::call
When ly:make-unpure-pure-container is called with a single procedure
argument, this procedure is used for both unpure and pure calls. It
turns out that the calling convention in call_pure_function places the
start/end arguments always in position 2/3 of the call.
Unpure_pure_call::call previously always dropped the last 2 arguments of
a pure call before passing the rest on. Most calls take exactly 3
arguments (grob start end) where this does not make a difference, but
there may be use cases with a different number of arguments.
James Lowe [Wed, 23 Sep 2015 07:46:19 +0000 (08:46 +0100)]
Doc: CG - remove link to R. Kainhofer's doc builds
This link no longer works
I have not been able to
find any equivalent on
Reinhold's own site and
had no reply when contacted
by email to confirm if this
link had moved or was now
deprecated.
David Kastrup [Wed, 16 Sep 2015 19:43:50 +0000 (21:43 +0200)]
Issue 4611: Don't give RepeatTieColumn a `cause' event
Rationale: the cause is used for point-and-click information and for
stuff like \parenthesize, and a RepeatTieColumn does not have metrics
that would be useful for that. In particular, this causes code like
{ c'1-\parenthesize\repeatTie }
to compile without spurious parens and error messages.
David Kastrup [Tue, 15 Sep 2015 18:50:13 +0000 (20:50 +0200)]
Issue 4609/4: Move \once action from iterators to listeners
This ends the dependency of the events generated for \once\unset and
\once\set on the current context (bad for recording and replaying events
like with the part combiner and quoted music). It also implements
\once\revert and makes every \once\override and \once\revert impervious
to any other overrides and reverts that may happen at the same time.
Most environments have "Nimbus Sans L" instead of "Nimbus Sans".
This commit replaces "Nimbus Sans" with the list of
"Nimbus Sans" and "Nimbus Sans L".
Most environments have "Nimbus Sans L" instead of "Nimbus Sans".
This commit replaces "Nimbus Sans" with the list of
"Nimbus Sans" and "Nimbus Sans L".
Issue 4591 / 1: Fix font-name overriding `Times New Roman'
A comma is required
for font name "Times New Roman"'s explicit termination.
If there is no comma, Pango interpret "Times New Roman" as
"Times New" family with "Roman" style.
Simon Albrecht [Tue, 8 Sep 2015 13:54:56 +0000 (14:54 +0100)]
Doc: NR - Improve wording in 'Changing Spacing'
Issue 4589
The paragraph from "Avoid (or reduce)"
in spacing.itely used 'for example'
twice in a row. The description of the
'volta bracket' issue was unclear in
terminology and phrasing.
David Kastrup [Sun, 6 Sep 2015 12:45:52 +0000 (14:45 +0200)]
Remove TODO comment about crashing music functions in .scm
After issue 4442, there is no lexical tie of #{...#} to the current parser,
and even before that, with standard parser/location arguments there should
not have been any problems after issue 3153 at the latest.
Thomas Morley [Sun, 23 Aug 2015 13:24:06 +0000 (15:24 +0200)]
Clear fret-diagram- and harp-pedal-input-strings from whitespace
issue 4575
Whitespace-characters are deleted before further processing.
Allows for
\markup \fret-diagram #"s:2;h:5;
6-3;5-5;4-5;3-4;2-3;1-x;"
Also adding errors for typos in fret-diagram with a meaningful message:
\markup \fret-diagram #"s:2;g:r;
6-3;5-5;4-5;3-4;2-3;1-x;"
will return:
fatal error: Unhandled entry in fret-diagram "g:r" in "g:r"
This error would not apply, if something for #\g would be defined
in fret-parse-definition-string somewhere in the future.
Then, the message would be:
fatal error: Unhandled entry in fret-diagram "r" in "g:r"
David Nalesnik [Wed, 26 Aug 2015 14:46:07 +0000 (09:46 -0500)]
Scheme function to draw lines based on grob layout
A number of C++ stencil callbacks use Line_interface::line to draw
lines based on line-interface properties defining a particular grob.
This allows control of aspects such as line style (based on the setting
of Grob.style) and fine-tuning of dashed lines through dash-fraction
and dash-period.
This patch gives access to Line_interface::line in Scheme through the
callback ly:line-interface::line. (The simpler name ly:line was ruled
out in an effort to distinguish it from other functions such as
ly:bracket and ly:circle which do not take a grob argument.) Users
will be able to create custom stencils with more functionality
(including rewriting certain C++ callbacks--such as Hairpin::print--to
allow for easy modifications without loss of capability.)
David Nalesnik [Mon, 24 Aug 2015 14:13:31 +0000 (09:13 -0500)]
Don't print redundant flags in chords
This patch adds a check to lily/stem-engraver.cc which ensures that only
one Flag grob appears for a given Stem grob. Previously, a flag was created
and printed for each note of a chord.