[Top][All Lists]

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

Re: skyline vs. y-aligned-side

From: Han-Wen Nienhuys
Subject: Re: skyline vs. y-aligned-side
Date: Fri, 26 Jan 2007 00:12:44 +0100
User-agent: Thunderbird (X11/20061219)

Joe Neeman escreveu:
> On 1/25/07, Han-Wen Nienhuys <address@hidden> wrote:
>> Hello Joe,
>> 2 questions
>> 1. do you see any reason to use
>>  ly:side-position-interface::y-aligned-side
>> for Y-offset callbacks on stuff that uses outside-staff-priority?
> It makes certain user-overrides a little easier. Since
> outside-staff-priority only ever pushes objects away from the staff,
> you could add extra padding to an outside-staff-priority object to
> give things a more uniform appearance, for example.

Ah, I thought it replaced the  y-positioning wholesale, but 
it starts from the position calculated by y-aligned-side  instead?

>> 2. it would be cool if it were possible to position several grobs as a
>> single outline. Right now, we use DynamicLineSpanner to ensure that
>> all related dynamics stay on one Y position, but I suspect that it
>> should be possible to use the outside-staff-prority stuff to do that.
>> Do you think you could pull that off? Of course, the grobs will be marked
>> so that it is possible to distinguish related  groups of dynamics.
>> The same holds for piano pedals. If we could do this, this would simplify
>> dynamics-engraver a lot, and we could scrap piano-pedal-align-engraver.
> Sure, I'll give that a try. As far as distinguishing related dynamics
> goes, what if each DynamicText (PianoPedal, etc.) just had a pointer
> to the next related one? Then you have a lot of flexibility (in the
> backend at least) because you can align arbitrary grob types (eg. a
> DynamicText with a VoltaBracket).

Sounds like a good idea. 


Han-Wen Nienhuys - address@hidden -

LilyPond Software Design
 -- Code for Music Notation

reply via email to

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