Patrick McCarty <pnor...@gmail.com> writes:
> 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.
This sounds to me like giving users a low-level manual way to fudge
around a bug/design mistake. This sounds like something that should
happen automatically in most cases.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
