Am 21.05.2015 um 15:21 schrieb Olivier Vogel:
2015-05-21 13:54 GMT+01:00 Kieren MacMillan
<kieren_macmil...@sympatico.ca <mailto:kieren_macmil...@sympatico.ca>>:
May I ask why you’re not using Lilypond’s built-in (and generallly
excellent) voice-handling? e.g. In the modified snippet (below),
I’m using \voiceOne, \voiceTwo, etc., which eliminates the need
for \stemUp, \tieDown, etc., and appears (to my eye) to eliminate
all note collisions.
Simply because, I'm learning Lilypond since only a few days.
Your solution avoids the collision at the third measure, but
introduces an horizontal shift at the fourth measure, which I'd like
to prevent. Is it possible?
p.s. Also note that I abstracted your note code from your score
code — it is so much easier to read and debug this way, in my
opinion, and it keeps the score block as clean and simple as possible.
Thank you very much for your advice. As a beginner, where can I learn
how to write a better code?
1. Learning by doing – and by trying yourself how you might improve it,
so that it’s more flexible, easy to type and read.
2. Use the templates of Frescobaldi <http://frescobaldi.org>, which
besides is extremely recommendable anyway.
3. Learn from others – look at code examples from experienced users like
in the LSR, like on this list, or elsewhere on the web (but there are
all sorts of code around, including less elegant or outdated ones…)
HTH and keep going :-),
Simon
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
