|
| From: | lilypond |
| Subject: | Re: Issue 1311 in lilypond: New spacing code affects user-created pseudo-staff contexts |
| Date: | Mon, 08 Nov 2010 10:51:38 +0000 |
Comment #4 on issue 1311 by v.villenave: New spacing code affects user-created pseudo-staff contexts
http://code.google.com/p/lilypond/issues/detail?id=1311I suspected as much. (What actually surprises me is that it didn't produce vertical space with 2.12.) The real problem here is that people whose code used to work with 2.12.3 may find themselves with suboptimal output when switching to 2.14.
Is there a way convert-ly can do it automatically, or at least print a NOT_SMART warning? (e.g. when detecting an \alias Staff or something?) Or we can just add a changes.tely item for staff-affinity so that we can tell unhappy users to RTFChangelog. What would you do?
| [Prev in Thread] | Current Thread | [Next in Thread] |