Thanks Dominic. I'll give that a try. Guy
On 7/31/2017 9:09 PM, Dominic wrote:
I believe it's because the second note does not naturally collide with any other, and has no cause to be 'forced' out of the way. Instead use /\once \override NoteColumn.X-offset/ for those notes. I'm sure another user will explain the technical reasons! -- View this message in context: http://lilypond.1069038.n5.nabble.com/Why-doesn-t-once-override-NoteColumn-force-hshift-work-on-more-than-one-note-in-a-measure-tp204756p204758.html Sent from the User mailing list archive at Nabble.com. _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
-- “Happiness is the meaning and the purpose of life, the whole aim and end of human existence.” ― Aristotle _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
