On 2015/06/28 00:17:58, Dan Eble wrote:
On 2015/06/27 19:45:12, thomasmorley651 wrote:
bassStaffProperties and trebleStaffProperties are not really
documented,
though
I'd call it more a documentation issue.
...
I vote for keeping them, although I think it's a very cumbersome
method to
Thank you James, LGTM.
Only one comment: did you forget to add this second suggestion?
2. in section Developer discussion recommend to send translation reports
to the translation mailing list:
email: translati...@lilynet.net
archive: http://lilypond-translations.3384276.n2.nabble.com/
LGTM
Trevor
https://codereview.appspot.com/252770043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
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
On 2015/06/28 12:30:21, Dan Eble wrote:
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.
Reviewers: ,
Description:
Auto_change_iterator: move some state from C++ to Scheme
This simplifies the iterator and prepares it for future combination
with partcomine code.
Please review this at https://codereview.appspot.com/248470043/
Affected files (+16, -21 lines):
M
Got it. That's the file data I saw that made me wonder. Makes perfect sense
now!
On Saturday, June 27, 2015, Masamichi Hosoda [via Lilypond]
ml-node+s1069038n178256...@n5.nabble.com wrote:
Greetings, Dev Team!
I was just browsing through some of the latest code (in scm/font.scm)
and I
