markpole...@gmail.com writes: > On 2014/06/06 09:29:03, Mark Polesky wrote: >> Please review this new patch. I'm not entirely sure this >> is the right approach, so I may need some advice here. > > This patch has gone through the review/countdown process without a > single comment or review, but I'm not comfortable pushing it without any > feedback. In the definition of \magnifyMusic (in > music-functions-init.ly), I've used about 50 temporary overrides, > manually entering scaled values based on the normal default values for > each grob-property I'm overriding. Ideally, if the user has already > modified some of those values, I'd like to base the new scaled values on > the user's choices, and not base them on the LilyPond default values. > If that's possible at all, I don't know how to do that.
If you do a read-modify-write on properties, you have to use \applyMusic for that. > https://codereview.appspot.com/103890046/ -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
