[Top][All Lists]

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

Re: [GSoC] spanners project update

From: Jan-Peter Voigt
Subject: Re: [GSoC] spanners project update
Date: Fri, 24 Jun 2016 15:34:17 +0200
User-agent: K-9 Mail for Android

Hi Nathan, hi Dan,

the "nearest" context might be on Staff level - or, if (for example) you have 
voices switching staves, on StaffGroup level, where a StaffGroup also might be 
a GrandStaff or the like. If the context property turns out to complex (I don't 
see all consequences yet), you'll have to use this static engraver member. But 
you should try the "nearest" context.


P.S. I am going on vacation this weekend, so I'll be online on monday again.

Am 24. Juni 2016 14:28:44 MESZ, schrieb Dan Eble <address@hidden>:
>> On Jun 24, 2016, at 07:41 , Nathan Chou <address@hidden> wrote:
>> Hello,
>> spanners with an id are handled as potentially being cross-voice.
>> engraver maintains a static list member (so it is shared between all
>> instances of an engraver) of named spanners and the voice each
>> currently belongs to.
>First, thanks for attacking this problem.
>Using a static member sounds like a convenient way to ramp up your
>work, but limiting in the number of ways it can be used and maintained.
>As soon as one tries to use this feature in a case in which there are
>concurrent but unrelated instances of those engravers, side effects not
>expected by the user will begin to appear.
>For the best solution, let your mentor advise you, but I suspect that
>the most Lilypondish way would be to store your index as a property in
>the nearest context that encloses all the voices you might want to
>lilypond-devel mailing list

Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

reply via email to

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