Re: Auto_change_iterator no longer creates staff contexts itself. They are created in scheme. (issue 249970043 by address@hidden)

[nine . fierce . ballads]

On 2015/06/28 11:17:58, thomasmorley651 wrote:

> Let me clearify, I don't insist in keeping those properties, though
I'd like to
> keep the possibility to simply write \autochange { ... } _and_ to have
the
> possibility to set the clefs in both staves.

What do you think about putting that enhancement into a ticket of its
own?  My only motivation to touch \autochange is to remove what I see as
unnecessary duplication in the innards of \partcombine and \autochange.

> The NR shows an example for \autochange { ... } and I think the
> treble/bassStaffProperties were meant to set the clefs.

Maybe, but the split point is hard-coded to middle C, isn't it?  So that
makes it a little weird with other clefs.  (Of course that could be
fixed as well.)


https://codereview.appspot.com/249970043/