Jan-Peter Voigt wrote > I added a snippet to open-lily-lib: > https://github.com/openlilylib/snippets/tree/master/editorial-tools/auto-transpose
Continuing with the late theme... :) Thanks for the snippet Jan-Peter, both as a way to use an engraver, and also the custom context properties. I had wondered about custom properties in the past, so it's nice to see an example of how to do it. I just did something similar (but for a different purpose) with a couple of custom grob properties added to the StaffSymbol grob. (Basically storing staff-specific "meta-data" type values per staff rather than in global variables.) While it's not difficult to copy and paste the code for defining context and grob properties (if you know where to look), I wonder if it might make sense to make these functions user-accessible? (i.e. define-public) Seems like that would be a simple change that would open up a number of possibilities like this snippet or for things like [1]. It would at least make them easier to do. (Maybe there are reasons not to do that that I'm not aware of?) [1] https://lists.gnu.org/archive/html/lilypond-user/2013-11/msg00256.html But that's another topic... Anyway, looks like this snippet might be a nice workaround until a more robust solution can be worked out. A small suggestion: what about using "input-concert-pitch" (or "input-in-concert-pitch") for your custom property name? That seems clearer than "music-concert-pitch" to me. Although I see in the readme file that you are rethinking things, so maybe this is a moot point. Cheers, -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/Transposing-instruments-in-orchestra-score-tp162176p162450.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
