Joram Berger wrote > Will it also look good for custom key signatures? Hi Joram,
Well, in your example, there will be no difference between the old and new coding: The first two naturals with full overlap get a maximum extra padding of 0.3, the second and third naturals are (vertically) so far apart that there will be no extra padding at all. In general, the algorithm can cope with custom key signatures as it compares the individual vertical distance between neighbouring naturals and decides whether to add extra padding (and how much) or not. The following illustration (linked from issue #5312) compares the old and new algorithm. <http://lilypond.1069038.n5.nabble.com/file/t3887/key_cancellation_intervals.png> Even if not all constellations that may occur in custom key signatures are directly shown, you can see that the algorithm (checking if the intervals marked in green touch, overlap or don't overlap) generally will work for any interval and thus for any custom key signature. All the best, Torsten -- Sent from: http://lilypond.1069038.n5.nabble.com/Dev-f88644.html _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
