2009/7/31 Joe Neeman <[email protected]>: > It should be sufficient to simply remove the definition of the Dynamics > context from these files (and the \accepts Dynamics part from > PianoStaff). The default Dynamics context is very similar (and drew > heavily from) the piano dynamics template, so it should be a drop-in > replacement.
A lot of users have been using a user-defined Dynamics context for years. How about making convert-ly print a warning whenever it finds a Dynamics context in a score? Something such as: "Warning: Please check if the user-defined Dynamic context is still needed, as recent versions of LilyPond implement it by default" Or a less verbose NOT_SMART_ENOUGH thingy... Regards, Valentin _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
