lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: \magnifyMusic stem-length enigma


From: Abel Cheung
Subject: Re: \magnifyMusic stem-length enigma
Date: Thu, 3 Jul 2014 17:52:00 +0800

The LilyPond doc has mentioned in scheme function section:

ly:context-pushpop-property context grob eltprop val
Do a single \override or \revert operation in context. The grob
definition grob is extended with eltprop (if val is specified) or
reverted (if unspecified).

So calling context-pushpop-property again without the value should be
able to revert the setting to previous state.



On Thu, Jul 3, 2014 at 5:44 PM, Mark Polesky <address@hidden> wrote:
> David Kastrup wrote:
>> I don't know how you are planning to do it.  It would be
>> my guess that it is hard to do in a manner that will
>> behave sensibly when you put that sort of construct into
>> quoted music.  It is probably already hard to do when
>> using \magnifyMusic in multiple parallel contexts since
>> you need to store the information somewhere.
>>
>> Perhaps most feasible is to just use \applyContext for
>> increasing fontSize by the given amount, and then use it
>> again at the end for decreasing by the same amount.  If
>> someone _sets_ fontSize in the middle then: tough.  But at
>> least you do not need to store the old value anywhere
>> then.
>
> Ha, that's exactly what I did:
> http://codereview.appspot.com/103890046/diff2/150001:210001/scm/music-functions.scm
>
> I just have one question: How do I do the equivalent of
> this...
>
>   \revert Tie.details.stem-gap
>
> ...using ly:context-pushpop-property?  I can't get it to
> revert *nested* grob-properties.  I get close, but then
> something always ends up wrong.  I don't think it's strictly
> needed in my case, but I'd like to know if there is a way.
>
> - Mark
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-devel



-- 
Abel Cheung
New GPG Key fingerprint: F43B 7F88 3D7B 4B58 928E  0151 EC2B E414 3B03 A8AC
Old GPG Key fingerprint: 671C C7AE EFB5 110C D6D1  41EE 4152 E1F1 C671 86FF



reply via email to

[Prev in Thread] Current Thread [Next in Thread]