2009/7/28 Mark Polesky :
> I intend to define a new context-property called
> "autochangeMargin" so that the user can do this sort of thing:
>
> \new PianoStaff \autochange \relative {
> \set autochangeMargin = #2
> c8 d e f g f e d
> c b a g f g a b
> c d e f g f e d
> }
Making this a contex
Okay, I'm almost finished with the autochange stuff (staff, not clef).
I like the current implementation, but the tweakable parameter called
"margin" on line 24 of autochange_revised.scm is for the moment stuck
there. So, for right now, if the user wants to change that parameter,
it must be done fr
On Wed, Jul 22, 2009, David Kastrup said:
> writes:
>
>> On Wed, Jul 22, 2009, Trevor Daniels said:
> There are instrument-dependent "thresholds of pain" involved: singers'
> clefs will just not change in midpiece. ...
actually, speaking as a singer with decades experience, they do change f
writes:
> On Wed, Jul 22, 2009, Trevor Daniels said:
>
>>> Anyway, I think that it would make a lot more sense if the staff
>>> were determined by the "average" pitch of the chord. And, I think
>>> I've solved this in the attached patch.
>
> What would make the most sense is to consider the rang
On Wed, Jul 22, 2009, Trevor Daniels said:
>> Anyway, I think that it would make a lot more sense if the staff
>> were determined by the "average" pitch of the chord. And, I think
>> I've solved this in the attached patch.
What would make the most sense is to consider the range of the intended
i
Mark Polesky wrote Wednesday, July 22, 2009 8:32 AM
In NR 2.2.1 Changing staff automatically, it says this:
Chords will not be split across the staves; they will be assigned
to a staff based on the first note named in the chord construct.
http://kainhofer.com/~lilypond/Documentation/user/lily
