[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Doc: NR 4.1.2: Reorganize vertical dimensions. (issue2316042)
From: |
Carl Sorensen |
Subject: |
Re: Doc: NR 4.1.2: Reorganize vertical dimensions. (issue2316042) |
Date: |
Sun, 3 Oct 2010 12:26:09 -0600 |
On 10/2/10 10:50 PM, "Joe Neeman" <address@hidden> wrote:
>
> On Sat, Oct 2, 2010 at 8:08 PM, <address@hidden> wrote:
>> On 2010/10/03 02:49:30, Mark Polesky wrote:
>>> On 2010/10/02 16:32:06, Carl wrote:
>>
>> I don't think so. I think 'padding is added as a rigid space interval,
>> hence my saying that it is added to the layout item above.
>>
>> 'space should begin below 'padding IIUC.
>
> The attachment point of 'space doesn't depend on 'padding (or
> 'minimum-distance). If you think in terms of springs, the beginning of one
> spring is always glued to the end of the previous one. 'padding and
> 'minimum-distance are only useful in determining the minimum lengths of the
> springs.
>
What is the difference between 'padding and 'minimum-distance, then?
>
>> Maybe. It may be that the most natural reference points aren't easily
>> available.
>
> The springs are always attached to the (0, 0) coordinate relative to each
> staff or markup. That is, each staff or markup draws itself and returns some
> stencil. The spacing code just attaches to the (0, 0) coordinate of that
> stencil. For staves, it's the middle staff line (unless you fiddle with
> line-positions). For markups, it used to be the baseline (I think). As long as
> the various drawing routines can be altered so that the stencil is drawn
> relative to its "most natural" reference point, then the spacing code will
> handle it.
>
>> I think we should document what we have, and make enhancement requests
>> for what we would *like* to have. I don't think the exercise of "write
>> the documents for what we wish we had and then change the code to match"
>> is the best way to proceed. But if Joe's ok with it, then my opinion is
>> irrelevant.
>
> I don't have a strong opinion on this point. If you want to document the
> desired behaviour and add a critical issue, I'll probably be able to fix it in
> a reasonable time frame.
Great!
Carl
- Doc: NR 4.1.2: Reorganize vertical dimensions. (issue2316042), markpolesky, 2010/10/02
- Re: Doc: NR 4.1.2: Reorganize vertical dimensions. (issue2316042), tdanielsmusic, 2010/10/02
- Re: Doc: NR 4.1.2: Reorganize vertical dimensions. (issue2316042), markpolesky, 2010/10/02
- Re: Doc: NR 4.1.2: Reorganize vertical dimensions. (issue2316042), Carl . D . Sorensen, 2010/10/02
- Re: Doc: NR 4.1.2: Reorganize vertical dimensions. (issue2316042), markpolesky, 2010/10/02
- Re: Doc: NR 4.1.2: Reorganize vertical dimensions. (issue2316042), Carl . D . Sorensen, 2010/10/02
- Re: Doc: NR 4.1.2: Reorganize vertical dimensions. (issue2316042), percival . music . ca, 2010/10/03
- Re: Doc: NR 4.1.2: Reorganize vertical dimensions. (issue2316042), percival . music . ca, 2010/10/03
- Re: Doc: NR 4.1.2: Reorganize vertical dimensions. (issue2316042), markpolesky, 2010/10/03
- Re: Doc: NR 4.1.2: Reorganize vertical dimensions. (issue2316042), markpolesky, 2010/10/03
- Re: Doc: NR 4.1.2: Reorganize vertical dimensions. (issue2316042), perpeduumimmobile, 2010/10/04