Hi David,
i'm writing just to let you know that the function changing arpeggio length:
offsetArpeggioPositions =
#(define-music-function (parser location offsets) (pair?)
#{
\override Arpeggio #'positions = #(lambda (grob)
(let* ((func (assoc-get 'positions (cdr
Janek Warchoł janek.lilyp...@gmail.com writes:
I wish it was possible to add context to grob name in a more
LilyPondish way (i.e. with a dot)
It is conceivable as a parser extension, like 3/4 is nowadays generally
read as '(3 . 4). One would turn aa.bb.cc (no spaces!) to #'(aa bb cc)
in the
On Wed, May 23, 2012 at 1:02 PM, David Kastrup d...@gnu.org wrote:
Janek Warchoł janek.lilyp...@gmail.com writes:
I wish it was possible to add context to grob name in a more
LilyPondish way (i.e. with a dot)
It is conceivable as a parser extension,
That's good news!
like 3/4 is nowadays
2012/5/23 Janek Warchoł janek.lilyp...@gmail.com:
On Wed, May 23, 2012 at 1:02 PM, David Kastrup d...@gnu.org wrote:
Janek Warchoł janek.lilyp...@gmail.com writes:
I wish it was possible to add context to grob name in a more
LilyPondish way (i.e. with a dot)
It is conceivable as a parser
On Wed, May 23, 2012 at 1:43 PM, Thomas Morley
thomasmorle...@googlemail.com wrote:
I tried it similar to `overrideProperty' from `music-functions-init.ly'
But I didn't manage to get rid of the -signs, when specifying the
coctext. Is this possible?
\version 2.15.38
offsetPositions =
Thomas Morley thomasmorle...@googlemail.com writes:
I tried it similar to `overrideProperty' from `music-functions-init.ly'
But I didn't manage to get rid of the -signs, when specifying the
coctext. Is this possible?
\version 2.15.38
offsetPositions =
#(define-music-function (parser
Hi David all,
i want to make arpeggios longer (so that they overshoot the chords a
bit). I've modified your offsetBeamPositions function to work on
Arpeggios instead of Beams (that was easy), but i'm quite surprised to
find that it doesn't work correctly with cross-staff arpeggios. Do
you have
Hi Janek,
On Sat, May 19, 2012 at 8:03 AM, Janek Warchoł janek.lilyp...@gmail.comwrote:
Hi David all,
i want to make arpeggios longer (so that they overshoot the chords a
bit). I've modified your offsetBeamPositions function to work on
Arpeggios instead of Beams (that was easy), but i'm
Hi David,
On Sat, May 19, 2012 at 3:30 PM, David Nalesnik
david.nales...@gmail.com wrote:
This isn't a bug: cross-staff arpeggios belong to a different context. In
your case, they are a part of PianoStaff, so the override will have no
impact.
Ah, silly me! Thank you very much!
And by the
Hi,
I am very much enjoying now to tweak slurs and other curves using
offsets instead of hardcoded control-points.
I wonder if it would be interesting to have a similar approach to grobs
with a positions property (e.g. beams).
While it is comparably easy to find usable #'positions for a beam
Hi Urs,
On Thu, May 17, 2012 at 5:08 AM, Urs Liska li...@ursliska.de wrote:
Hi,
I am very much enjoying now to tweak slurs and other curves using offsets
instead of hardcoded control-points.
I wonder if it would be interesting to have a similar approach to grobs
with a positions property
11 matches
Mail list logo
