[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cross-staff versions of \arpeggioArrowUp etc.
From: |
Patrick McCarty |
Subject: |
Re: cross-staff versions of \arpeggioArrowUp etc. |
Date: |
Tue, 28 Jul 2009 23:36:40 -0700 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
On Tue, Jul 28, 2009 at 10:42:47PM -0700, Mark Polesky wrote:
>
> \arpeggioArrowUp etc. doesn't work with cross-staff arpeggios
> because the arpeggio-direction property is overridden at the
> Voice level, and not the PianoStaff level. To facilitate this
> situation for users, I propose adding these four commands to
> ly/property-init.ly:
>
> connectArpeggioArrowUp = {
> \revert PianoStaff.Arpeggio #'stencil
> \revert PianoStaff.Arpeggio #'X-extent
> \override PianoStaff.Arpeggio #'arpeggio-direction = #UP
> }
> connectArpeggioArrowDown = {
> \revert PianoStaff.Arpeggio #'stencil
> \revert PianoStaff.Arpeggio #'X-extent
> \override PianoStaff.Arpeggio #'arpeggio-direction = #DOWN
> }
> connectArpeggioNormal = {
> \revert PianoStaff.Arpeggio #'stencil
> \revert PianoStaff.Arpeggio #'X-extent
> \revert PianoStaff.Arpeggio #'arpeggio-direction
> \revert PianoStaff.Arpeggio #'dash-definition
> }
> connectArpeggioBracket = {
> \revert PianoStaff.Arpeggio #'X-extent
> \override PianoStaff.Arpeggio #'stencil = #ly:arpeggio::brew-chord-bracket
> }
>
> [snip]
>
> Good idea? Bad idea? Support? Opposition?
Sure! I wasn't aware of this limitation, and I think users would
greatly benefit from having these predefined commands.
I think the names are great too, but let's see what others think.
Thanks,
Patrick