Re: Attaches bound info to beam for better normalized-endpoint calculations. (issue4605047)

[address@hidden]

On Jun 23, 2011, at 12:31 AM, Neil Puttock wrote:

> On 22 June 2011 22:48, address@hidden <address@hidden> wrote:
> 
>> In this present case, I could see the bound info being calculated via a 
>> callback that fetches the 'quantized position property for the Y values, but 
>> the X values would still need to be calculated by consulting the normal 
>> stems à la lines 559-570.  Were I to place the calculation in a callback, it 
>> would require a code dup of these lines.  To avoid this, I could create a 
>> property called x-positions and change the name of positions to y-positions 
>> and quantized positions to quantized-y-positions.  Then, I'd put lines 
>> 559-570 in a separate callback for the X positions.  Lemme know if this 
>> sounds good.
> 
> I think I'd rather you keep the slightly unidiomatic code than rename
> properties (particularly since renaming positions will affect other
> grobs).

Fair 'nuf.  All of this stems from the feature of Beams whereby coordinates are 
calculated in terms of X/Y instead of left/right - I think it's the only 
spanner that will pose this problem.

Cheers,
MS